dbcve.org
TeamcityApplication · Jetbrains

CVE-2023-38064

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 2023.05.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 2023.05.1 build chain parameters of the "password" type could be written to the agent log

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

In JetBrains TeamCity versions prior to 2023.05.1, build chain parameters configured with the 'password' type were being written in plaintext to agent logs. This exposes sensitive credentials to anyone with access to the agent log files, creating a confidentiality breach where passwords could be recovered by unauthorized parties.

MitigationUpgrade TeamCity to version 2023.05.1 or later, which addresses the improper logging of password-type parameters. After upgrading, audit existing logs for any previously exposed credentials and rotate any passwords that may have been disclosed.

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:< 2023.05.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 server version
    Navigate to TeamCity Administration > Server Administration > Server Configuration, or access the 'About' page in the TeamCity UI to view the exact version number
    Affected if The installed version is earlier than 2023.05.1
  2. Identify password-type parameters in build configurations
    Review build configurations and build chain settings in TeamCity. Go to Project > Build Configurations > Parameters tab and look for parameters with 'password' type specified in the parameter type dropdown
    Affected if Any build configurations or build chains contain parameters configured with the 'password' type
  3. Inspect agent build logs for plaintext credentials
    Access build logs from completed builds on the build agents. Navigate to a specific build > Build Log. Search the log content for any plaintext password strings or look for patterns matching your configured password-type parameter names
    Affected if Build agent logs contain plaintext passwords or sensitive credential values in the log output
  4. Review historical and artifact logs
    Examine archived build logs, build artifacts, and any exported or copied log files from previous builds that may have been stored or shared
    Affected if Historical log files contain plaintext passwords from builds that occurred before upgrading to 2023.05.1 or later

A user is affected if their TeamCity version is before 2023.05.1 AND they have password-type parameters in their build configurations, as these credentials would have been written in plaintext to agent logs.

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 2023.05.1 or later
Fixed in 2023.05.1
Interim mitigation

Upgrade TeamCity to version 2023.05.1 or later, which addresses the improper logging of password-type parameters. After upgrading, audit existing logs for any previously exposed credentials and rotate any passwords that may have been disclosed.

Recommended fix High confidence

2023.05.1

  1. Backup your current TeamCity installation and database before proceeding with the upgrade
  2. Download TeamCity 2023.05.1 from the official JetBrains website (www.jetbrains.com)
  3. Stop the TeamCity server and agents
  4. Follow the standard TeamCity upgrade procedure for your installation method
  5. Start the TeamCity server and verify it runs correctly
  6. Test that password-type parameters are no longer written to agent logs

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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