CVE-2022-44623
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 version before 2022.10, Project Viewer could see scrambled secure values in the MetaRunner settings
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 before 2022.10, users with the Project Viewer role could see scrambled secure values in MetaRunner settings. This constitutes an information disclosure vulnerability where sensitive configuration values were exposed to unauthorized low-privilege users.
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< 2022.10CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 dashboard and navigate to 'About' or check the server startup logs for the version numberAffected if The version is listed as anything before 2022.10 (e.g., 2022.09, 2022.04, etc.)
-
Check for Project Viewer role usageNavigate to User Management in TeamCity admin and review roles assigned to users; look for any users explicitly assigned the Project Viewer roleAffected if Any user accounts have the Project Viewer role assigned
-
Review MetaRunner configurations for secure valuesNavigate to Administration > MetaRunners and inspect each MetaRunner for parameters marked as 'password', 'secure', or 'hidden' type valuesAffected if MetaRunners exist that contain secure/password type parameters storing sensitive values
-
Verify Project Viewer access to MetaRunner settingsAs a user with Project Viewer role (only), attempt to view MetaRunner configurations and observe whether scrambled/encoded secure values are visible in the settingsAffected if A Project Viewer user can access and view MetaRunner settings containing visible (even if scrambled) secure parameter values
Your environment is affected if you run any TeamCity version before 2022.10 AND have MetaRunners with secure values configured AND have users assigned the Project Viewer role, as the vulnerability allows low-privilege Project Viewers to see scrambled secure values in MetaRunner settings.
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 · scoped2022.10
Upgrade TeamCity to version 2022.10 or later to remediate this vulnerability.
2022.10 or later
- 1. Create a full backup of the TeamCity data directory and database before upgrading
- 2. Download TeamCity 2022.10 or later from the official JetBrains website
- 3. Stop the TeamCity server gracefully
- 4. Run the TeamCity installer/upgrade on the server
- 5. Start the TeamCity server after upgrade completes
- 6. Verify that Project Viewer role can no longer see scrambled secure values in MetaRunner settings
- 7. Review server logs for any upgrade-related errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44623 — 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-2022-44623 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