cve.bz

CVE-2006-5201 sun

no score yetEPSS 3.5%Fix available

sun: no CVSS score yet. EPSS 3.5% estimated probability of exploitation activity in the next 30 days.

On this page
Multiple packages on Sun Solaris, including (1) NSS; (2) Java JDK and JRE 5.0 Update 8 and earlier, SDK and JRE 1.4.x up to 1.4.2_12, and SDK and JRE 1.3.x up to 1.3.1_19; (3) JSSE 1.0.3_03 and earlier; (4) IPSec/IKE; (5) Secure Global Desktop; and (6) StarOffice, when using an RSA key with exponent 3, removes PKCS-1 padding before generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents these products from correctly verifying X.509 and other certificates that use PKCS #1.
EPSS
3.5% (unchanged from 3.5% a week ago; 3.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2006-5201 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2006-5201?via=ask-ai-copy and https://cve.bz/cve/CVE-2006-5201?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2006-5201 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sun:solaris9.0
sun:solaris10.0
sun:sunos5.8
sun:jdk1.5.0
sun:jdk1.5.0:update1
sun:jdk1.5.0:update2
sun:jdk1.5.0:update3
sun:jdk1.5.0:update4
sun:jdk1.5.0:update5
sun:jdk1.5.0:update6
sun:jdk1.5.0:update7
sun:jdk1.5.0:update7_b03
sun:jdk1.5.0:update8
sun:jre1.3.1
sun:jre1.3.1_2
sun:jre1.3.1_03
sun:jre1.3.1_04
sun:jre1.3.1_05
sun:jre1.3.1_06
sun:jre1.3.1_07
sun:jre1.3.1_08
sun:jre1.3.1_09
sun:jre1.3.1_10
sun:jre1.3.1_11
sun:jre1.3.1_12
sun:jre1.3.1_13
sun:jre1.3.1_14
sun:jre1.3.1_15
sun:jre1.3.1_16
sun:jre1.3.1_17
sun:jre1.3.1_18
sun:jre1.3.1_19
sun:jre1.4.2
sun:jre1.4.2_1
sun:jre1.4.2_2
sun:jre1.4.2_3
sun:jre1.4.2_4
sun:jre1.4.2_5
sun:jre1.4.2_6
sun:jre1.4.2_7
sun:jre1.4.2_8
sun:jre1.4.2_9
sun:jre1.4.2_10
sun:jre1.4.2_11
sun:jre1.4.2_12
sun:jre1.5.0
sun:jre1.5.0:update1
sun:jre1.5.0:update2
sun:jre1.5.0:update3
sun:jre1.5.0:update4
sun:jre1.5.0:update5
sun:jre1.5.0:update6
sun:jre1.5.0:update7
sun:jre1.5.0:update8
sun:sdk1.3.1
sun:sdk1.3.1_01
sun:sdk1.3.1_01a
sun:sdk1.3.1_02
sun:sdk1.3.1_03
sun:sdk1.3.1_04
sun:sdk1.3.1_05
sun:sdk1.3.1_06
sun:sdk1.3.1_07
sun:sdk1.3.1_08
sun:sdk1.3.1_09
sun:sdk1.3.1_10
sun:sdk1.3.1_11
sun:sdk1.3.1_12
sun:sdk1.3.1_13
sun:sdk1.3.1_14
sun:sdk1.3.1_15
sun:sdk1.3.1_16
sun:sdk1.3.1_17
sun:sdk1.3.1_18
sun:sdk1.3.1_19
sun:sdk1.4.2
sun:sdk1.4.2_1
sun:sdk1.4.2_2
sun:sdk1.4.2_3
sun:sdk1.4.2_4
sun:sdk1.4.2_5
sun:sdk1.4.2_6
sun:sdk1.4.2_7
sun:sdk1.4.2_8
sun:sdk1.4.2_9
sun:sdk1.4.2_10
sun:sdk1.4.2_11
sun:sdk1.4.2_12
sun:jsse1.0.3
sun:jsse1.0.3_01
sun:jsse1.0.3_02
sun:jsse1.0.3_03

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux3nssno fix listedAZL-112997

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

References

Check your stackJSON