CVE-2023-38067
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 2023.05.1 build 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 confidenceThis is an information disclosure vulnerability in JetBrains TeamCity where build parameters configured with the 'password' type were being written in plain text to agent logs, exposing sensitive 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< 2023.05.1CVSS 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.
-
Check TeamCity server versionNavigate to Administration > Server Administration > Server Configuration, or check the About page at /about.html. Locate the version number displayed.Affected if The installed version is earlier than 2023.05.1
-
Identify password-type build parametersReview all build configurations in Projects > [Project Name] > Build Configurations > Parameters tab. Look for parameters where the Type is set to 'Password'.Affected if Any build configuration contains parameters with the 'password' type defined
-
Examine agent logs for plaintext credentialsLocate agent log files (typically in <TeamCity Agent>/logs/ directory). Search log files for instances of parameter names that were configured as 'password' type, looking for plaintext values appearing after the parameter name.Affected if Any agent logs contain plaintext values matching password-type parameter names from your build configurations
You are affected if your TeamCity version is below 2023.05.1 AND you use password-type build parameters, as their values may have been written in plaintext to agent logs.
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 · scoped2023.05.1
Upgrade TeamCity to version 2023.05.1 or later, and rotate any credentials that may have been logged prior to the upgrade.
2023.05.1 or later
- Download TeamCity version 2023.05.1 or later from the official JetBrains website
- Review the TeamCity upgrade documentation for your current version
- Back up your existing TeamCity data and configuration
- Stop the TeamCity server and agents
- Install the new version following the standard upgrade procedure
- Start the TeamCity server and verify the upgrade was successful
- Verify that password-type build parameters are no longer written to agent logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38067 — 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-2023-38067 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