Information Disclosure in phantom-html-to-pdf (CVE-2020-7763)
Summary
Vulnerability in phantom-html-to-pdf (CVE-2020-7763). Confidential information can be exposed externally. Mitigation: upgrade to 0.6.2 or later.
Original description
The description as published by the source.
This affects the package phantom-html-to-pdf before 0.6.1.
PoC
var fs = require('fs') var conversion = require("phantom-html-to-pdf")();
conversion.allowLocalFilesAccess = false conversion({
html: "document.write(window.location='c:/windows/win.ini')"
}, function(err, pdf) {
var output = fs.createWriteStream('output.pdf') console.log(pdf.logs);
console.log(pdf.numberOfPages);
pdf.stream.pipe(output);
});
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-7763 has been found in phantom-html-to-pdf.
Confidential information can be exposed externally.
What to do: upgrade phantom-html-to-pdf to 0.6.2 or later.
If unsure, ask your IT team or search "phantom-html-to-pdf CVE-2020-7763" on the vendor's site.
CVE-2020-7763 (phantom-html-to-pdf) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in phantom-html-to-pdf.
Check the vendor advisory for the affected versions of phantom-html-to-pdf.
Severity: ?. Confidential information can be exposed externally.
Update to 0.6.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'phantom-html-to-pdf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'phantom-html-to-pdf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
phantom-html-to-pdfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade phantom-html-to-pdf to 0.6.2ステージング環境で 0.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web snyk.io
- web npmjs.com