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

> Local attackers can access sensitive data, modify information, or cause denial of service on HP Smart Zero Client devices.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m5f3-m3cw-jgjf

## What is CVE-2013-2339?

CVE-2013-2339 is a medium-severity vulnerability in n/a, published on 29 Jun 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HP Smart Zero Core 4.3 and 4.3.1 on the t410 All-in-One Smart Zero Client, t410 Smart Zero Client, t510 Flexible Thin Client, t5565z Smart Client, t610 Flexible Thin Client, and t610 PLUS Flexible Thin Client allows local users to obtain sensitive information, modify data, or cause a denial of service via unknown vectors.

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

It affects 1 product.


Products: Hp Smart Zero Core.

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

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

## Is CVE-2013-2339 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2124](https://insights.sbomify.com/CVE-2015-2124/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2339 is a medium-severity vulnerability in n/a, published on 29 Jun 2013. 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-2339 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-2339/ (Markdown: https://insights.sbomify.com/CVE-2013-2339/index.md)
```

## Sources

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

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