CVE-2006-4339
No exploitation reported by the sources we read.
- Published2006-09-05
- WeaknessCWE-310 · CWE-347
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A flaw was found in OpenSSL. When configured to use an RSA key with exponent 3, OpenSSL improperly removes PKCS-1 padding before generating a hash. This allows remote attackers to forge PKCS #1 v1.5 signatures. Consequently, OpenSSL may incorrectly verify X.509 and other certificates, leading to a bypass of trust and authentication mechanisms.
Timeline
dates in UTC- 2006-09-0517:04CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-31 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2006-4339?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2006-4339?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.9 | ≤ 0.9.7 | no fix published | NVD |
| 0.9 | = 0.9.1c | no fix published | NVD |
| 0.9 | = 0.9.2b | no fix published | NVD |
| 0.9 | = 0.9.3 | no fix published | NVD |
| 0.9 | = 0.9.3a | no fix published | NVD |
| 0.9 | = 0.9.4 | no fix published | NVD |
| 0.9 | = 0.9.5 | no fix published | NVD |
| 0.9 | = 0.9.5a | no fix published | NVD |
| 0.9 | = 0.9.6 | no fix published | NVD |
| 0.9 | = 0.9.6a | no fix published | NVD |
| 0.9 | = 0.9.6b | no fix published | NVD |
| 0.9 | = 0.9.6c | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- secunia.comPatch · Vendor Advisory
- secunia.comVendor Advisory
- secunia.comVendor Advisory
- secunia.comVendor Advisory
- secunia.comVendor Advisory
- secunia.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.1read 2026-10-31
- NVDCVSS 2.04.3read 2026-10-31
- NVDweakness (CWE)CWE-310, CWE-347read 2026-10-31
- FIRST EPSSEPSS score5.1 %2026-10-30
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2006-09-05
- Last Modified
- 2026-10-30
- NVD status
- Modified
Frequently asked questions
What is CVE-2006-4339?
Is CVE-2006-4339 actively exploited?
What is the CVSS score for CVE-2006-4339?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.