CVE-2024-47161
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 · uneditedIn JetBrains TeamCity before 2024.07.3 password could be exposed via Sonar runner REST API
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 · moderate confidenceIn JetBrains TeamCity versions prior to 2024.07.3, passwords could be exposed through the Sonar runner REST API. This likely occurs when sensitive credentials are transmitted or logged via API responses during SonarQube integration workflows.
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< 2024.07.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamCity versionAccess the TeamCity administration UI, go to 'Administration' > 'Server Administration' > 'Server Information', or query the server root page for the version numberAffected if The displayed version is lower than 2024.07.3 (for example, 2024.07.2, 2024.07.1, 2024.06.x, or earlier)
-
Determine if SonarQube integration is configuredNavigate to 'Administration' > 'Plugins' > 'Installed Plugins' and look for the SonarQube/Runner plugin, or check project build configurations for SonarQube scanner stepsAffected if SonarQube integration is enabled and the TeamCity server processes Sonar analysis requests
-
Review API access logs for Sonar runner endpointsExamine TeamCity server logs and HTTP access logs for requests to REST API endpoints related to sonar-runner, specifically looking for API response payloads that may contain password or credential dataAffected if Log entries or API responses show plain-text passwords or sensitive credentials in SonarQube-related API calls
You are affected if your TeamCity version is below 2024.07.3 AND you have SonarQube integration enabled, as the combination allows credential exposure through the Sonar runner REST API.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2024.07.3
Upgrade TeamCity to version 2024.07.3 or later to obtain the patch. Review and rotate any credentials that may have been exposed through this API vector.
2024.07.3
- Backup your TeamCity database and configuration files before upgrading
- Download TeamCity 2024.07.3 or later from the official JetBrains website (www.jetbrains.com)
- Stop the TeamCity server service
- Run the TeamCity installer or deploy the new version following standard upgrade procedures
- Start the TeamCity server and verify the upgrade was successful
- Verify that the Sonar runner REST API no longer exposes passwords
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47161 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47161 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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