Response integrity loss via missing HTTP headers
Published Nov 9, 2021 · Updated Aug 4, 2024
HTTP security-header omission in JetBrains TeamCity before 2021.1.2 allows remote attackers to affect response integrity. Neither JetBrains nor the CVE record identifies which headers are absent, which responses omit them, or what request processing causes the omission. The issue is network-reachable without authentication or user interaction, but public records identify only limited response-integrity impact.
Summary
What happened
HTTP security-header omission in JetBrains TeamCity before 2021.1.2 allows remote attackers to affect response integrity. Neither JetBrains nor the CVE record identifies which headers are absent, which responses omit them, or what request processing causes the omission. The issue is network-reachable without authentication or user interaction, but public records identify only limited response-integrity impact.
The record
- CVE
- CVE-2021-43195
- Published
- Nov 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No sourced classifications are available.
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