Signature forgery via incorrect DSA upper-bound check
Published Oct 26, 2023 · Updated Feb 13, 2025
Improper DSA signature verification in Browserify browserify-sign 2.6.0 through 4.2.1 allows remote attackers to forge signatures. The dsaVerify checkValue helper compares b.cmp(q) with q instead of zero, so an s value equal to q passes validation and makes the signature (1, q) verify under any public key. Exploitation requires an application to verify attacker-supplied DSA signatures, and the resulting trust bypass is limited to decisions that rely on that verification.
Summary
What happened
Improper DSA signature verification in Browserify browserify-sign 2.6.0 through 4.2.1 allows remote attackers to forge signatures. The dsaVerify checkValue helper compares b.cmp(q) with q instead of zero, so an s value equal to q passes validation and makes the signature (1, q) verify under any public key. Exploitation requires an application to verify attacker-supplied DSA signatures, and the resulting trust bypass is limited to decisions that rely on that verification.
The record
- CVE
- CVE-2023-46234
- Published
- Oct 26, 2023
- Updated
- Feb 13, 2025
- Vendor
- Browserify
- Product
- browserify-sign
- Classifications
- CWE-347, CAPEC-475
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 26, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=>= 2.6.0, <= 4.2.1
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
- Upstream forged DSA signature regression testproof of concept · demonstrated
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