# CVE-2014-10002: Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vectors.


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qxp8-qj2v-85pr

## What is CVE-2014-10002?

CVE-2014-10002 is a medium-severity vulnerability in Jetbrains Teamcity, published on 13 Jan 2015. 

### Official description

Unspecified vulnerability in JetBrains TeamCity before 8.1 allows remote attackers to obtain sensitive information via unknown vectors.

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

It affects 1 product.


Products: Jetbrains Teamcity.

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

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

## Is CVE-2014-10002 being exploited?

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

## Other vulnerabilities in Jetbrains Teamcity

- [CVE-2026-63077](https://insights.sbomify.com/CVE-2026-63077/): JetBrains TeamCity Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2024-27198](https://insights.sbomify.com/CVE-2024-27198/): JetBrains TeamCity Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2023-42793](https://insights.sbomify.com/CVE-2023-42793/): JetBrains TeamCity Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-27199](https://insights.sbomify.com/CVE-2024-27199/): JetBrains TeamCity Relative Path Traversal (high 7.3, exploited in the wild)
- [CVE-2024-23917](https://insights.sbomify.com/CVE-2024-23917/): Auth bypass in TeamCity (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-10002 is a medium-severity vulnerability in Jetbrains Teamcity, published on 13 Jan 2015. 
Exploitation: There is no known exploitation of CVE-2014-10002 in the wild and no public exploit code.

Affected product: Jetbrains Teamcity. 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-10002/ (Markdown: https://insights.sbomify.com/CVE-2014-10002/index.md)
```

## Sources

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

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