CVE-2012-1772 json
Unspecified vulnerability in the Oracle Outside In Technology component in Oracle Fusion Middleware 8.3.5 and 8.3.7 allows context-dependen…
published 2012-07-17 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1782
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Oracle Outside In Technology component in Oracle Fusion Middleware 8.3.5 and 8.3.7 allows context-dependent attackers to affect availability via unknown vectors related to Outside In Filters, a different vulnerability than CVE-2012-1766, CVE-2012-1767, CVE-2012-1769, CVE-2012-1770, CVE-2012-1771, CVE-2012-1773, CVE-2012-3106, CVE-2012-3107, CVE-2012-3108, and CVE-2012-3110.
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-058
vendor-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2012/ms12-067
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2013:150
vendor-advisory
-
oracle.com
/technetwork/topics/security/cpujul2012-392727.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15323
vdb-entry, signature
-
securityfocus.com
/bid/54497
vdb-entry
- blogs.technet.com /b/srd/archive/2012/07/24/more-information-on-security-advisory-2737111.aspx
-
securitytracker.com
/id?1027264
vdb-entry
- www-01.ibm.com /support/docview.wss?uid=swg21660640
-
kb.cert.org
/vuls/id/118913
third-party-advisory, us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/77005
vdb-entry
- technet.microsoft.com /security/advisory/2737111
Sources
- CVE List CVE-2012-1772
- NVD CVE-2012-1772
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.