jose4j: Insecure iteration count setting
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat AMQ Streams 2.6.0 | |||
| jose4j | cpe:/a:redhat:amq_streams:2 | RHSA-2023:7678 | 2023-12-06T00:00:00Z |
| Red Hat build of Quarkus 2.13.9.Final | |||
| org.bitbucket.b_c/jose4j:0.9.3.redhat-00004 | cpe:/a:redhat:quarkus:2.13::el8 | RHSA-2023:7700 | 2023-12-07T00:00:00Z |
| Red Hat Data Grid 8.4.6 | |||
| jose4j | cpe:/a:redhat:jboss_data_grid:8 | RHSA-2023:7676 | 2023-12-06T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2687 | jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less. |
Github GHSA |
GHSA-7g24-qg88-p43q | jose4j uses weak cryptographic algorithm |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.766% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.