CVE-2011-3517 json
Unspecified vulnerability in the Oracle OpenSSO component in Oracle Sun Products Suite 8.0 allows remote attackers to affect availability v…
published 2011-10-18 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3480
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.5%
- EPSS 3.5% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Oracle OpenSSO component in Oracle Sun Products Suite 8.0 allows remote attackers to affect availability via unknown vectors related to Authentication.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-3517 updated cvss 4.3
OpenSSO: unspecified vulnerability in the authentication component
-
Red Hat JBoss SOA Platform 5.3fixed: vendor fix RHSA-2012:1125
-
Red Hat JBoss BRMS 5 unspecified unspecifiednot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.51% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
References
-
oracle.com
/technetwork/topics/security/cpuoct2011-330135.html
patch, vendor-advisory
-
rhn.redhat.com
/errata/RHSA-2012-1232.html
vendor-advisory
-
secunia.com
/advisories/46527
third-party-advisory
-
secunia.com
/advisories/50084
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/70793
vdb-entry
-
osvdb.org
/76459
vdb-entry
-
securityfocus.com
/bid/50208
vdb-entry
Sources
- CVE List CVE-2011-3517
- NVD CVE-2011-3517
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.