Affected versions
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk11-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk17-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
Red HatRed Hat JBoss Enterprise Application Platform 7/jboss-eap-7/eap74-els-openjdk8-openshift-rhel8
- Affected versions
- Unknown
- Fixed version
- Not reported
- Affected versions
- Unknown
- Fixed version
- Not reported
Exploitation
Description
In Bouncy Castle for Java before 1.85, S/MIME validator trusts signer-asserted signingTime for path validation. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcmail-fips and bcjmail-fips 1.0.7 (1.0.X series), 2.0.7 (2.0.X series) and 2.1.7 (2.1.X series).
A flaw was found in Bouncy Castle for Java. The S/MIME (Secure/Multipurpose Internet Mail Extensions) validator improperly trusts the signing time asserted by the signer during path validation. This could allow an attacker to bypass certificate path validation, potentially leading to the acceptance of invalid or expired certificates. Such an issue can compromise the integrity of signed data.

