# CVE-2013-6493: Information disclosure in n/a

> Local attackers can read Java applet-browser messages by pre-creating a predictable temporary socket file in IcedTea-Web.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-6493, GHSA-5rjx-hhcc-fqph, MGASA-2014-0049, RHBA-2014:1417

## What is CVE-2013-6493?

CVE-2013-6493 is a low-severity vulnerability in n/a, published on 3 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The LiveConnect implementation in plugin/icedteanp/IcedTeaNPPlugin.cc in IcedTea-Web before 1.4.2 allows local users to read the messages between a Java applet and a web browser by pre-creating a temporary socket file with a predictable name in /tmp.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-6493?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `icedtea-web` | Red Hat:enterprise_linux:6::client | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-javadoc` | Red Hat:enterprise_linux:6::client | All versions | 0:1.5.1-1.el6 |
| `icedtea-web` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-javadoc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:1.5.1-1.el6 |
| `icedtea-web` | Red Hat:enterprise_linux:6::server | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-javadoc` | Red Hat:enterprise_linux:6::server | All versions | 0:1.5.1-1.el6 |
| `icedtea-web` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.5.1-1.el6 |
| `icedtea-web-javadoc` | Red Hat:enterprise_linux:6::workstation | All versions | 0:1.5.1-1.el6 |

Products: Redhat Icedtea-Web.

## How do I fix CVE-2013-6493?

Upgrade to a fixed version.

## Is CVE-2013-6493 being exploited?

There is no known exploitation of CVE-2013-6493 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-3423](https://insights.sbomify.com/CVE-2012-3423/): Memory corruption in n/a (high 7.5)
- [CVE-2011-0706](https://insights.sbomify.com/CVE-2011-0706/): Privilege escalation in n/a (high 7.5)
- [CVE-2011-2514](https://insights.sbomify.com/CVE-2011-2514/): Security feature bypass in n/a (medium 6.8)
- [CVE-2012-3422](https://insights.sbomify.com/CVE-2012-3422/): Memory corruption in n/a (medium 6.8)
- [CVE-2011-2513](https://insights.sbomify.com/CVE-2011-2513/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6493 and fix it if it is affected.

What it is: CVE-2013-6493 is a low-severity vulnerability in n/a, published on 3 Mar 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6493 in the wild and no public exploit code.

Affected product: n/a. 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-2013-6493/ (Markdown: https://insights.sbomify.com/CVE-2013-6493/index.md)
```

## Sources

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

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