CVE-2013-3770 json
Unspecified vulnerability in the Oracle WebCenter Content component in Oracle Fusion Middleware 10.1.3.5.1, 11.1.1.6.0, and 11.1.1.7.0 allo…
published 13y ago modified 4mo ago also EUVD-2013-3703
- cvss
- 5.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in the Oracle WebCenter Content component in Oracle Fusion Middleware 10.1.3.5.1, 11.1.1.6.0, and 11.1.1.7.0 allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Content Server. NOTE: the previous information is from the October 2013 CPU. Oracle has not commented on claims from a third party that the issue is related to "iDoc script injection" in the (1) cs and (2) urm components, which allows attackers to read "sensitive" files, as demonstrated by obtaining the "AES encryption key and encrypted credentials" of the weblogic user.
Is CVE-2013-3770 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
References
-
oracle.com
/technetwork/topics/security/cpujuly2013-1899826.html
vendor-advisory
-
verisigninc.com
/en_US/products-and-services/network-intelligence-availability/idefense/public-vulnerability-reports/articles/
third-party-advisory
-
secunia.com
/advisories/54227
third-party-advisory
-
osvdb.org
/95271
vdb-entry
-
securityfocus.com
/bid/61228
vdb-entry
-
securitytracker.com
/id/1028801
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/85658
vdb-entry
Sources
- CVE List CVE-2013-3770
- NVD CVE-2013-3770
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.