CVE-2022-44646
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, no audit items were added upon editing a user's 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 prior to 2022.10, editing a user's settings (such as permissions, roles, or profile information) does not generate corresponding audit log entries. This creates a gap in the security audit trail where administrative or self-service user modifications go unrecorded, preventing detection of unauthorized or suspicious user account changes.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Determine installed TeamCity versionNavigate to Administration > Server Administration > Server Configuration, or check the login page footer which displays the version number. Alternatively, access the <TeamCity data directory>/logs/teamcity-server.log file and search for version information.Affected if The installed version is any version prior to 2022.10 (for example, 2022.09, 2022.04, 2022.03, etc.)
-
Access the Audit Log viewerLog in as an administrator and navigate to Administration > Audit Log. This page displays recorded system events.Affected if The Audit Log page is inaccessible or returns no entries when users have been edited in the past.
-
Trigger a test user settings change and verify audit entryAs an administrator, edit a test user's profile (such as changing a role, permission, or email address), then immediately check the Audit Log for a corresponding entry under the User Management or Users section.Affected if After modifying user settings, no new audit entry appears in the Audit Log for that user change.
-
Review audit log configuration for user eventsNavigate to Administration > Server Administration > Audit Log Settings (or equivalent configuration area) and examine which event categories are enabled for logging.Affected if User-related audit events are not selected or the audit logging feature is disabled entirely.
A user is affected if their TeamCity version is below 2022.10 AND the Audit Log does not record user settings modifications after such edits occur.
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 where audit logging for user settings edits has been implemented. Additionally, implement compensating controls such as external monitoring of user account changes through database auditing or integration with SIEM tools until the upgrade is completed.
2022.10 or later
- 1. Back up your current TeamCity data and configuration files
- 2. Download TeamCity 2022.10 or later from the official JetBrains website
- 3. Stop the TeamCity server
- 4. Install the new version following the official upgrade documentation
- 5. Start the TeamCity server
- 6. Verify that audit logging is now working for user settings changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-44646 — 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-44646 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