# CVE-2015-1613: Information disclosure in n/a

> Authenticated users can access sensitive API keys and data via specific API methods in RhodeCode.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qc99-q2vr-37hj, PYSEC-2015-33

## What is CVE-2015-1613?

CVE-2015-1613 is a medium-severity vulnerability in n/a, published on 16 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

RhodeCode before 2.2.7 allows remote authenticated users to obtain API keys and other sensitive information via the (1) update_repo, (2) get_locks, or (3) get_user_groups API method.

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

## Which versions are affected by CVE-2015-1613?

1 open source package ship an affected version, including rhodecode. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rhodecode` | PyPI | All versions | 2.2.7 |

Products: Rhodecode Rhodecode Enterprise.

## How do I fix CVE-2015-1613?

Upgrade rhodecode to 2.2.7 or later.

## Is CVE-2015-1613 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1613 and fix it if it is affected.

What it is: CVE-2015-1613 is a medium-severity vulnerability in n/a, published on 16 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1613 in the wild and no public exploit code.

Affected packages and fixed versions:
- rhodecode (PyPI): affected all versions; fixed in 2.2.7

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-2015-1613/ (Markdown: https://insights.sbomify.com/CVE-2015-1613/index.md)
```

## Sources

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

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