Skip to content
Fencer Intel
medium 5.5

CVE-2024-35301 json

In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token

published 2y ago modified 4mo ago also EUVD-2024-35272

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

Summary

In JetBrains TeamCity before 2024.03.1 commit status publisher didn't check project scope of the GitHub App token

Patch / fix

  • JetBrains TeamCity 2024.03.1

Is CVE-2024-35301 in your stack? 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
NVD 3.1 5.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Affected products

  • JetBrains TeamCity

Classification

Weakness
  • CWE-280 Improper Handling of Insufficient Permissions or Privileges

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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.