Skip to content
Fencer Intel
medium 5.5

CVE-2015-0260 json

RhodeCode and Kallithea are vulnerable to sensitive information disclosure

published 11y ago modified 4mo ago also GHSA-hhx9-4vw2-x54r , PYSEC-2015-29 , PYSEC-2015-32 , EUVD-2015-0027

cvss
5.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

RhodeCode before 2.2.7 and Kallithea 0.1 allows remote authenticated users to obtain API keys and other sensitive information via the get_repo API method.

Patch / fix

  • pypi rhodecode 2.2.7
  • pypi kallithea 0.2

Is CVE-2015-0260 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.86% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • kallithea-scm.org https://kallithea-scm.org/security/cve-2015-0260.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/oss-sec/2015/q1/505 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi rhodecode
<2.2.7
2.2.7
pypi kallithea
<0.2
0.2

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.