# CVE-2014-4210: Information disclosure in n/a

> Remote attackers can compromise confidentiality in Oracle WebLogic Server via Web Services vectors, requiring immediate patching.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r9q5-qcf6-7r92

## What is CVE-2014-4210?

CVE-2014-4210 is a medium-severity vulnerability in Oracle Fusion Middleware, published on 17 Jul 2014. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle WebLogic Server component in Oracle Fusion Middleware 10.0.2.0 and 10.3.6.0 allows remote attackers to affect confidentiality via vectors related to WLS - Web Services.

## Which versions are affected by CVE-2014-4210?

It affects 1 product.


Products: Oracle Fusion Middleware.

## How do I fix CVE-2014-4210?

No fix has been published for CVE-2014-4210 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-4210 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4210 exists.

Public exploit code:

- weblogic 漏洞扫描工具。目前包含对以下漏洞的检测能力：CVE-2014-4210、CVE-2016-0638、CVE-2016-3510、CVE-2017-3248、CVE-2017-3506、CVE-2017-10271、CVE-2018-2628、CVE-2018-2893、CVE-2018-2894、CVE-2018-3191、CVE-2018-3245、CVE-2018-3252、CVE-2019-2618、CVE-2019-2725、CVE-2019-2729、CVE-2019-2890、CVE-2020-2551、CVE-2020-14750、CVE-2020-14882、CVE-2020-14883 (github_poc): https://github.com/daybreak-kits/weblogicScanner
- CVE-2014-4210+Redis未授权访问 (github_poc): https://github.com/NoneNotNull/SSRFX
- Weblogic SearchPublicRegistries SSRF(CVE-2014-4210) Exploit Script based on Python3 (github_poc): https://github.com/NHPT/WebLogic-SSRF_CVE-2014-4210
- CVE-2014-4210 SSRF PORTSCANNER PoC (github_poc): https://github.com/unmanarc/CVE-2014-4210-SSRF-PORTSCANNER-POC
- https://github.com/ZorvithonLeo/Exploit-CVE-2014-4210- (github_poc): https://github.com/ZorvithonLeo/Exploit-CVE-2014-4210-
- Oracle Weblogic - Server-Side Request Forgery (nuclei): http/cves/2014/CVE-2014-4210.yaml

## Other vulnerabilities in Oracle Fusion Middleware

- [CVE-2012-1710](https://insights.sbomify.com/CVE-2012-1710/): Oracle Fusion Middleware Unspecified (critical 9.8, exploited in the wild)
- [CVE-2012-3152](https://insights.sbomify.com/CVE-2012-3152/): Oracle Fusion Middleware Unspecified (critical 9.1, exploited in the wild)
- [CVE-2012-0518](https://insights.sbomify.com/CVE-2012-0518/): Oracle Fusion Middleware Unspecified (medium 4.7, exploited in the wild)
- [CVE-2013-2380](https://insights.sbomify.com/CVE-2013-2380/): Other in n/a (critical 10.0)
- [CVE-2012-3135](https://insights.sbomify.com/CVE-2012-3135/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4210 and fix it if it is affected.

What it is: CVE-2014-4210 is a medium-severity vulnerability in Oracle Fusion Middleware, published on 17 Jul 2014. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-4210 exists.

Affected product: Oracle Fusion Middleware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-4210/ (Markdown: https://insights.sbomify.com/CVE-2014-4210/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-4210
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-4210
- OSV: https://osv.dev/vulnerability/CVE-2014-4210

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-4210/
Summaries are generated and may contain mistakes; the official description above is the record.