Remote code execution via unsafe PAC code generation
Published Aug 24, 2021 · Updated Sep 17, 2024
Improper code generation in pac-resolver before 5.0.0 allows remote attackers to execute code via untrusted PAC files. The resolver passes PAC-derived JavaScript through the degenerator compiler and sandbox path without safely constraining generated code, allowing attacker-controlled script execution. Exploitation requires an application to process attacker-supplied PAC data; successful execution can compromise confidentiality, integrity, and availability.
Summary
What happened
Improper code generation in pac-resolver before 5.0.0 allows remote attackers to execute code via untrusted PAC files. The resolver passes PAC-derived JavaScript through the degenerator compiler and sandbox path without safely constraining generated code, allowing attacker-controlled script execution. Exploitation requires an application to process attacker-supplied PAC data; successful execution can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2021-23406
- Published
- Aug 24, 2021
- Updated
- Sep 17, 2024
- Vendor
- TooTallNate
- Product
- pac-resolver
- Classifications
- T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=unspecified <5.0.0
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
No public exploit references are available in this record.
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