CVE-2022-24337
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 2021.2, health items of pull requests were shown to users who lacked appropriate permissions.
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 before version 2021.2, an authorization flaw allowed pull request health item information to be displayed to users who lacked the appropriate permissions to view them, leading to potential information disclosure of sensitive CI/CD pipeline details.
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.2CVSS 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 versionNavigate to TeamCity server administration (typically /admin/admin.html?item=server) or use the server diagnostics to determine the installed version numberAffected if The installed version is any version prior to 2021.2
-
Check for pull request integrationsReview project VCS root configurations to see if pull request health features or integrations (such as GitHub, GitLab, or Bitbucket Cloud PR decorators) are enabledAffected if Pull request health items are configured in any project
-
Audit user permissions on pull request dataExamine which users and groups have access to project settings and build features, specifically checking if users without project administration or viewing all permissions can see pull request health informationAffected if Users lacking full project permissions can access or view pull request health item details
The environment is affected if running any TeamCity version below 2021.2 with pull request health features enabled and users who should not have access can view PR health data
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 · scoped2021.2
Upgrade TeamCity to version 2021.2 or later. Alternatively, review user permissions and access controls to ensure unauthorized users cannot access pull request health data in affected versions.
2021.2 or later
- Back up the TeamCity data directory and database before proceeding with any upgrade
- Stop the TeamCity server
- Download TeamCity 2021.2 or later from the official JetBrains download page
- Install the new version following the official TeamCity upgrade documentation
- Start the TeamCity server and verify the upgrade was successful
- Confirm that pull request health items are now properly restricted to users with appropriate permissions
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-24337 — 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-24337 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