Weakened password protection via low PBES2 iterations
Published Oct 24, 2023 · Updated Sep 11, 2024
Weak cryptography in jose4j before 0.9.3 allows remote attackers to weaken PBES2 password protection through low iteration counts. PBES2 processing accepts an iteration count of 1000 or less without enforcing a secure minimum, reducing the cost of password-based key derivation. An application must process attacker-controlled encrypted JWT parameters using a password-based key; the reduced work factor makes password recovery attacks more feasible.
Summary
What happened
Weak cryptography in jose4j before 0.9.3 allows remote attackers to weaken PBES2 password protection through low iteration counts. PBES2 processing accepts an iteration count of 1000 or less without enforcing a secure minimum, reducing the cost of password-based key derivation. An application must process attacker-controlled encrypted JWT parameters using a password-based key; the reduced work factor makes password recovery attacks more feasible.
The record
- CVE
- CVE-2023-31582
- Published
- Oct 24, 2023
- Updated
- Sep 11, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-331, CWE-327, T1110.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 2023CVE publishedPublication date reported by the CVE source.
- Sep 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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