dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-24461

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In JetBrains TeamCity before 2024.12.1 decryption of connection secrets without proper permissions was possible via Test Connection endpoint

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Test Connection endpoint in JetBrains TeamCity versions before 2024.12.1 allowed unauthorized decryption of connection secrets (such as database passwords, API keys) without proper permission validation. An attacker could exploit this to obtain sensitive credentials stored in TeamCity's configuration.

MitigationUpgrade to TeamCity 2024.12.1 or later which contains the fix for proper authorization checks on the Test Connection endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamcityApplication
Affected:= 2024.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed TeamCity version
    Access the TeamCity Administration > Diagnostics page or check the version.txt file in the TeamCity home directory to determine the running version
    Affected if The installed version is earlier than 2024.12.1 (such as 2024.12.0, 2024.11.x, or earlier releases)
  2. Verify Test Connection endpoint accessibility
    Check if the /app/rest/buildTypes/testConnection REST endpoint or the Test Connection UI feature is accessible without authentication or with low-privilege user accounts
    Affected if The endpoint responds without requiring elevated privileges beyond standard user authentication
  3. Inspect connection configurations
    Review stored connection configurations (database, API keys, VCS roots) in the TeamCity data directory or via the Administration > Connections page
    Affected if Sensitive connection configurations exist and the Test Connection feature can be invoked by unauthorized users to trigger decryption
  4. Check authorization settings
    Examine TeamCity user/group permissions, specifically whether non-administrator users have access to the Test Connection functionality
    Affected if Users without administrator privileges can access or execute the Test Connection feature on sensitive connections

You are affected if your TeamCity installation version is before 2024.12.1 AND the Test Connection endpoint is accessible to users who should not have permission to decrypt stored credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TeamCity 2024.12.1 or later which contains the fix for proper authorization checks on the Test Connection endpoint.

Recommended fix High confidence

TeamCity 2024.12.1

  1. 1. Back up your current TeamCity installation and database before proceeding
  2. 2. Download TeamCity 2024.12.1 from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. 3. Stop the TeamCity server service
  4. 4. Install or upgrade to version 2024.12.1 following the standard TeamCity upgrade documentation
  5. 5. Start the TeamCity server and verify the application runs correctly
  6. 6. Test the 'Test Connection' endpoint to confirm the authorization fix is working
  7. 7. Verify that connection secrets now require proper permissions to decrypt
Caveat Standard upgrade - review JetBrains release notes for any configuration changes between your current version and 2024.12.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24461 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data