CVE-2022-44622
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 between 2021.2 and 2022.10 access permissions for secure token health items were excessive
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 confidenceIn JetBrains TeamCity versions 2021.2 through 2022.10, access permissions for secure token health items were configured too permissively, potentially allowing unauthorized users to view sensitive token-related health information that should have been restricted.
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>= 2021.2, < 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 versionNavigate to TeamCity Administration > About page or check the version from the server startup logsAffected if The installed version is 2021.2.x through 2022.10.0 (versions before 2022.10.1)
-
Verify health item endpoint existsAccess the TeamCity health report interface, typically at /health/item/ or via the Administration > Server Health sectionAffected if The server health interface is accessible and displays health items
-
Confirm token health items are presentLook for health items related to 'secure token' or 'token' in the health report listingAffected if Health items containing token-related information are visible in the health report
-
Test unauthorized access to health itemsUsing a user account with limited or viewer-level permissions (not administrators), attempt to access the health item URLs or health report pagesAffected if A non-administrator user can view token-related health information that should be restricted
You are affected if TeamCity version is 2021.2 or higher but lower than 2022.10.1 AND the secure token health items are visible to users without administrative privileges.
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.1 or later which contains the fix for this excessive access permission issue.
TeamCity 2022.10 or later
- 1. Identify the current TeamCity version by navigating to Administration > Global Settings
- 2. Plan the upgrade to TeamCity 2022.10 or later version
- 3. Review JetBrains upgrade documentation for your deployment type (tar.gz or Windows installer)
- 4. Create a full backup of the TeamCity data directory and database
- 5. Test the upgrade in a staging environment before production deployment
- 6. Execute the upgrade following standard TeamCity upgrade procedures
- 7. Verify the upgrade was successful and the server is operational
- 8. Confirm the access permissions for secure token health items are now properly restricted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44622 — 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-44622 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