CVE-2011-4577: OpenSSL before 0.9.8s and 1.x before 1.0.0f, when RFC 3779 support is enabled, allows remote attackers to cause a denial of service…
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.1% (FIRST EPSS); higher than 94.9% of all records.
- Fixed version: openssl (Debian:12) 1.0.0f-1; openssl (Red Hat:enterprise_linux:6::client) 0:1.0.0-20.el6_2.1; openssl-debuginfo (Red Hat:enterprise_linux:6::client) 0:1.0.0-20.el6_2.1.
Low priority for now. Upgrade to openssl (Debian:12) 1.0.0f-1; openssl (Red Hat:enterprise_linux:6::client) 0:1.0.0-20.el6_2.1; openssl-debuginfo (Red Hat:enterprise_linux:6::client) 0:1.0.0-20.el6_2.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
OpenSSL before 0.9.8s and 1.x before 1.0.0f, when RFC 3779 support is enabled, allows remote attackers to cause a denial of service (assertion failure) via an X.509 certificate containing certificate-extension data associated with (1) IP address blocks or (2) Autonomous System (AS) identifiers.
- Published
- Jan 5, 2012
- Updated
- Jun 16, 2026
- EPSS
- 8.1% · 94th percentile
- CWE
- CWE-399
Report tools
Action score
19
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 8.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openssl opensslup to 1.0.0e inclusive
- openssl opensslup to 0.9.8r inclusive
- openssl openssl0.9.1c
- openssl openssl0.9.2b
- openssl openssl0.9.4
- openssl openssl0.9.5
- openssl openssl0.9.5a
- openssl openssl0.9.6
+12 more rows
- openssl openssl0.9.6a
- openssl openssl0.9.6b
- openssl openssl0.9.6c
- openssl openssl0.9.6d
- openssl openssl0.9.6e
- openssl openssl0.9.6f
- openssl openssl0.9.6g
- openssl openssl0.9.6h
- openssl openssl0.9.6i
- openssl openssl0.9.6j
- openssl openssl0.9.6k
- openssl openssl0.9.6l
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | openssl | before 1.0.0f-1 | 1.0.0f-1 |
| Red Hat:enterprise_linux:6::client | openssl | before 0:1.0.0-20.el6_2.1 | 0:1.0.0-20.el6_2.1 |
| Red Hat:enterprise_linux:6::client | openssl-debuginfo | before 0:1.0.0-20.el6_2.1 | 0:1.0.0-20.el6_2.1 |
| Red Hat:enterprise_linux:6::client | openssl-devel | before 0:1.0.0-20.el6_2.1 | 0:1.0.0-20.el6_2.1 |
| Red Hat:enterprise_linux:6::client | openssl-perl | before 0:1.0.0-20.el6_2.1 | 0:1.0.0-20.el6_2.1 |
| Red Hat:enterprise_linux:6::client | openssl-static | before 0:1.0.0-20.el6_2.1 | 0:1.0.0-20.el6_2.1 |
| Red Hat:enterprise_linux:6::hypervisor | rhev-hypervisor6 | before 0:6.2-20120209.0.el6_2 | 0:6.2-20120209.0.el6_2 |
| Red Hat:enterprise_linux:6::hypervisor | rhev-hypervisor6-tools | before 0:6.2-20120209.0.el6_2 | 0:6.2-20120209.0.el6_2 |
| SUSE:Linux Enterprise Desktop 12 | libqt4 | before 4.8.6-7.1 | 4.8.6-7.1 |
| SUSE:Linux Enterprise Desktop 12 | libqt4-sql-plugins | before 4.8.6-7.1 | 4.8.6-7.1 |
| SUSE:Linux Enterprise Software Development Kit 12 | libqt4-devel-doc | before 4.8.6-7.3 | 4.8.6-7.3 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2011-4109Jan 5, 2012 · Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an…42Plan
- ← EarlierCVE-2011-4576Jan 5, 2012 · The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher…24Monitor
- Later →CVE-2011-4619Jan 5, 2012 · The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:openssl | 1.0.0f-1 · Debian:12 | Package registry (OSV) |
| red hat:openssl | 0:1.0.0-20.el6_2.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-debuginfo | 0:1.0.0-20.el6_2.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-devel | 0:1.0.0-20.el6_2.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-perl | 0:1.0.0-20.el6_2.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-static | 0:1.0.0-20.el6_2.1 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:rhev-hypervisor6 | 0:6.2-20120209.0.el6_2 · Red Hat:enterprise_linux:6::hypervisor | Package registry (OSV) |
| red hat:rhev-hypervisor6-tools | 0:6.2-20120209.0.el6_2 · Red Hat:enterprise_linux:6::hypervisor | Package registry (OSV) |
| suse:libqt4 | 4.8.6-7.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
| suse:libqt4-devel-doc | 4.8.6-7.3 · SUSE:Linux Enterprise Software Development Kit 12 | Package registry (OSV) |
| suse:libqt4-sql-plugins | 4.8.6-7.1 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:N/AC:M/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (11 more)Show less
- lists.apple.com/archives/security-announce/2013/Jun/msg00000.html
- lists.fedoraproject.org/pipermail/package-announce/2012-November/092905.html
- lists.opensuse.org/opensuse-security-announce/2012-01/msg00017.html
- lists.opensuse.org/opensuse-security-announce/2012-01/msg00018.html
- marc.info/?l=bugtraq&m=132750648501816&w=2
- marc.info/?l=bugtraq&m=134039053214295&w=2
- secunia.com/advisories/57353
- support.apple.com/kb/HT5784
- www-01.ibm.com/support/docview.wss?uid=ssg1S1004564
- www.kb.cert.org/vuls/id/737740
- www.openssl.org/news/secadv_20120104.txt
Vendor advisories and official records. Exploit/PoC links are deliberately left out.