Remote code execution via test endpoint evaluation
Published Feb 29, 2024 · Updated Aug 26, 2024
Code injection in pdfmake 0.2.9's developer playground allows remote attackers to execute arbitrary code through its /pdf endpoint. The POST handler passes req.body.content to the Function constructor and immediately invokes the resulting function to obtain a document definition. The endpoint is absent from the npm package and exists only when the separate, intentionally unsafe test server is installed and exposed; the maintainers therefore dispute that pdfmake is vulnerable.
Summary
What happened
Code injection in pdfmake 0.2.9's developer playground allows remote attackers to execute arbitrary code through its /pdf endpoint. The POST handler passes req.body.content to the Function constructor and immediately invokes the resulting function to obtain a document definition. The endpoint is absent from the npm package and exists only when the separate, intentionally unsafe test server is installed and exposed; the maintainers therefore dispute that pdfmake is vulnerable.
The record
- CVE
- CVE-2024-25180
- Published
- Feb 29, 2024
- Updated
- Aug 26, 2024
- Vendor
- pdfmake project
- Product
- pdfmake
- Classifications
- CWE-94, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Snyk crafted POST proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo