Java: PKIX Trust Engines Exhibit Critical Flaw In Trusted Names Evaluation
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 |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat JBoss A-MQ 6.2 | |||
| cpe:/a:redhat:jboss_amq:6.2.0 | RHSA-2015:1177 | 2015-06-23T00:00:00Z | |
| Red Hat JBoss Fuse 6.2 | |||
| cpe:/a:redhat:jboss_fuse:6.2.0 | RHSA-2015:1176 | 2015-06-23T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-2952 | The PKIX trust engines in Shibboleth Identity Provider before 2.4.4 and OpenSAML Java (OpenSAML-J) before 2.6.5 trust candidate X.509 credentials when no trusted names are available for the entityID, which allows remote attackers to impersonate an entity via a certificate issued by a shibmd:KeyAuthority trust anchor. |
Github GHSA |
GHSA-78fq-w796-q537 | Improper Certificate Validation in Shibboleth Identity Provider and OpenSAML |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.247% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.