Audit trail evasion via omitted user-setting events
Published Nov 3, 2022 · Updated May 2, 2025
Audit logging omission in JetBrains TeamCity before 2022.10 allows remote authenticated users to edit user settings without audit records. The audit subsystem fails to append an item when user settings are saved; JetBrains has not disclosed the responsible function or code path. Exploitation requires high-privilege authenticated access and affects audit-trail integrity rather than confidentiality or availability.
Summary
What happened
Audit logging omission in JetBrains TeamCity before 2022.10 allows remote authenticated users to edit user settings without audit records. The audit subsystem fails to append an item when user settings are saved; JetBrains has not disclosed the responsible function or code path. Exploitation requires high-privilege authenticated access and affects audit-trail integrity rather than confidentiality or availability.
The record
- CVE
- CVE-2022-44646
- Published
- Nov 3, 2022
- Updated
- May 2, 2025
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-223
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 3, 2022CVE publishedPublication date reported by the CVE source.
- May 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022.10 <2022.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo