CVE-2019-12841
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 · uneditedIncorrect handling of user input in ZIP extraction was detected in JetBrains TeamCity. The issue was fixed in TeamCity 2018.2.2.
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 confidencePath traversal vulnerability in TeamCity's ZIP extraction functionality allows attackers to write files to arbitrary filesystem locations during archive extraction through specially crafted ZIP archives containing files with '..' sequences in their paths.
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.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/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.
-
Identify TeamCity installation locationLocate the TeamCity server directory - common paths include /opt/teamcity, C:\TeamCity, or /usr/local/TeamCity on Linux. Check for the TeamCity web application root directory.Affected if TeamCity is installed and the installation directory cannot be found for version verification.
-
Determine installed TeamCity versionCheck the version file located at <TeamCity_home>/buildAgent/target/webapps/ROOT/WEB-INF/buildServer.properties or the main server version file. Alternatively, access the TeamCity web interface and navigate to Administration > Server Administration > About to view the exact version number.Affected if The installed version is less than 2018.2.2 (for example, 2018.2.1, 2018.1.x, 10.x, 9.x, etc.).
-
Confirm ZIP artifact handling is in useReview TeamCity build configurations to identify any that download, extract, or process ZIP archives as part of their build steps. Check build logs for recent builds that involved ZIP file extraction or artifact publishing.Affected if TeamCity processes ZIP archives in any build configuration - this is the vulnerable feature.
-
Check server logs for signs of path traversalExamine TeamCity server logs in <TeamCity_home>/logs/teamcity-server.log for entries containing '../' or '..\' patterns in file paths, especially related to archive extraction operations.Affected if Log entries show unusual path sequences like ../../../ indicating potential exploitation attempts.
You are affected if your TeamCity version is below 2018.2.2 AND your server handles ZIP archive extraction as part of build processes.
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 data2018.2.2
Upgrade TeamCity to version 2018.2.2 or later. Prior to upgrade, assess current TeamCity configuration and ensure backup of all build configurations and data.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12841 — 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-12841 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