CVE-2023-38062
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 parameters of the "password" type could be shown in the UI in certain composite build configurations
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 confidenceIn JetBrains TeamCity versions prior to 2023.05.1, parameters configured with the 'password' type were incorrectly displayed in the web UI when used within composite build configurations, exposing sensitive credential values to unauthorized users who could view build configuration pages.
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.
-
Identify TeamCity server versionNavigate to Administration > Server Administration > Server Information in the web UI, or access the /about.html endpoint to view the installed version numberAffected if The version shown is earlier than 2023.05.1 (e.g., 2023.04.x, 2022.x, etc.)
-
Check for composite build configurationsNavigate to Administration > Projects and locate build configurations that use the 'Composite' build run type, or query the database for build_type records with the composite_run_type parameterAffected if Any composite build configurations exist in the TeamCity instance
-
Identify password-type parameters in composite buildsNavigate to each composite build configuration > Parameters tab and look for parameters with the 'password' type configured, or inspect the build configuration XML/JSON for parameters of type 'password'Affected if Password-type parameters are defined in composite build configurations
-
Verify password parameter visibility in UILog in as a non-privileged user or view the composite build configuration page as an unauthorized user and check if password parameter values are displayed in plain text rather than maskedAffected if Password values are visible (not masked) in the web UI for composite build configurations
The environment is affected if TeamCity version is earlier than 2023.05.1 AND composite build configurations exist with password-type parameters that are visible in the web UI to unauthorized users.
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 to resolve the password parameter exposure in composite build configurations.
TeamCity 2023.05.1 or later
- Upgrade TeamCity to version 2023.05.1 or later to resolve the password parameter information exposure vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38062 — 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-38062 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