dbcve.org
TeamcityApplication · Jetbrains

CVE-2025-57734

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 2025.07.1 or later.
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 2025.07.1 aWS credentials were exposed in Docker script files

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 confidence

In JetBrains TeamCity versions prior to 2025.07.1, AWS credentials were being written to Docker script files in an insecure manner, allowing unauthorized access to those credentials. This is an information disclosure vulnerability where sensitive cloud service credentials are exposed in plaintext within script files.

MitigationUpgrade TeamCity to version 2025.07.1 or later to patch the vulnerability. Additionally, immediately rotate any AWS credentials that may have been exposed and audit Docker script files for hardcoded credentials.

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:< 2025.07.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 TeamCity version
    Locate the TeamCity installation and identify the version number, typically visible in the administration UI or in the version metadata file. Compare it to the affected range: any version prior to 2025.07.1 is vulnerable.
    Affected if Installed version is less than 2025.07.1
  2. Determine if AWS integration is enabled
    Review TeamCity project configurations and build steps to identify whether any AWS-related features such as AWS CodeDeploy, AWS Elastic Beanstalk, or AWS-related build runners are configured.
    Affected if AWS cloud integration features are in use with TeamCity versions prior to 2025.07.1
  3. Inspect Docker script files for plaintext credentials
    Search the TeamCity server file system for Docker-related script files (such as .sh, .ps1, or Dockerfile files created by TeamCity build processes) and examine their contents for hardcoded AWS access key IDs, secret access keys, or AWS profile credentials.
    Affected if Docker script files contain plaintext AWS credentials (access key IDs beginning with AKIA, or secret access keys)
  4. Audit build logs and temporary directories
    Review TeamCity build logs and temporary working directories for any traces of AWS credentials that may have been written during build execution involving Docker-based AWS deployments.
    Affected if Build logs or temp directories contain exposed AWS credentials

A user is affected if running any TeamCity version prior to 2025.07.1 with AWS cloud integration features enabled, where Docker script files may contain plaintext AWS 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
Upgrade available Upgrade to 2025.07.1 or later
Fixed in 2025.07.1
Interim mitigation

Upgrade TeamCity to version 2025.07.1 or later to patch the vulnerability. Additionally, immediately rotate any AWS credentials that may have been exposed and audit Docker script files for hardcoded credentials.

Recommended fix High confidence

TeamCity 2025.07.1 or later

  1. 1. Back up your existing TeamCity installation and database before upgrading.
  2. 2. Download TeamCity 2025.07.1 or later from the official JetBrains website.
  3. 3. Stop the running TeamCity server.
  4. 4. Install the new version following the standard upgrade procedure for your deployment method (Windows installer, tar.gz, Docker, etc.).
  5. 5. Start the TeamCity server and verify the upgrade completed successfully.
  6. 6. Review Docker build configurations to ensure no credentials remain exposed in script files.
  7. 7. Rotate any AWS credentials that may have been exposed as a precautionary measure.
Caveat Review release notes for 2025.07.1 for any configuration or feature changes that may affect your setup

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-57734 — 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-57734 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