CVE-2019-15038
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 · uneditedAn issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was fixed in TeamCity 2019.1.
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 confidenceThe TeamCity server version 2018.2.4 was not implementing certain security-related HTTP headers, which could allow attackers to perform cross-site scripting, clickjacking, or other client-side attacks. The specific headers missing were not disclosed in the advisory.
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= 2018.2.4CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Check TeamCity server versionLog into TeamCity as administrator and navigate to Administration > Server Administration > Server Information to view the exact version. Alternatively, inspect the teamcity-server.log file in the <TeamCity_home>/logs directory for version information at startup.Affected if The installed version is exactly 2018.2.4
-
Verify Content-Security-Policy headerSend an HTTP request to the TeamCity server (e.g., curl -I https://<your-teamcity-host> or use browser DevTools Network tab) and inspect the response headers for the Content-Security-Policy header.Affected if The Content-Security-Policy header is missing from server responses
-
Verify X-Frame-Options headerExamine the same HTTP response headers from the TeamCity server for the X-Frame-Options header.Affected if The X-Frame-Options header is missing from server responses
-
Verify Strict-Transport-Security headerCheck the HTTP response headers for the Strict-Transport-Security header when accessing TeamCity over HTTPS.Affected if The Strict-Transport-Security header is missing from server responses
You are affected if the installed TeamCity version is exactly 2018.2.4 and any of the security headers (Content-Security-Policy, X-Frame-Options, or Strict-Transport-Security) are missing from HTTP responses.
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.
From vendor dataUpgrade to TeamCity 2019.1 or later where the issue was fixed, or manually configure security-related HTTP headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security on the web server.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15038 — 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-2019-15038 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