jsrsasign: Improper Verification of Cryptographic Signature
CVE-2022-25898 is a critical-severity improper verification of cryptographic signature vulnerability in jsrsasign, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 10.5.25 as the first without the flaw, so updating jsrsasign to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.15% chance of exploitation within 30 days, higher than 67% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update jsrsasign to 10.5.25 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.7 | High | CNA (snyk.io) |
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 7.5 | High | NVD |
Official description
The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT signature with non Base64URL encoding special characters or number escaped characters may be validated as valid by mistake. Workaround: Validate JWS or JWT signature if it has Base64URL and dot safe string before executing JWS.verify() or JWS.verifyJWT() method.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/kjur/jsrsasign/commit/4536a6e9e8bcf1a644ab7c07ed96e453347dae41Third Party Advisory
- github.com/kjur/jsrsasign/releases/tag/10.5.25Release Notes, Third Party Advisory
- snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2935898Exploit, Third Party Advisory
- snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBKJUR-2935897Exploit, Third Party Advisory
- snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2935896Exploit, Third Party Advisory
- snyk.io/vuln/SNYK-JS-JSRSASIGN-2869122Exploit, Third Party Advisory
Other vulnerabilities in jsrsasign
- 7.5 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Recent Improper Verification of Cryptographic Signature vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.4 High severity
- 8.1 High severity
Spotted an error? Tell us.