LiveActive security incident?Get immediate response
CVE Record

CVE-2019-12844: A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages.

A possible stored JavaScript injection was detected on one of the JetBrains TeamCity pages. The issue was fixed in TeamCity 2018.2.3.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns a possible stored JavaScript injection in JetBrains TeamCity. If a vulnerable TeamCity page stored attacker-controlled script, users viewing it could be exposed to browser-side actions. The public record only states the issue was fixed in TeamCity 2018.2.3, with no severity score or affected version range.

Executive priority

Treat as a hygiene-driven update item unless internal exposure or legacy TeamCity use raises urgency. The lack of severity, KEV status, and technical detail prevents a stronger risk rating from the supplied evidence.

Technical view

CVE-2019-12844 describes a possible stored JavaScript injection on one JetBrains TeamCity page. Sources do not name the page, input vector, required privileges, CVSS score, CWE, or exact vulnerable versions. The only explicit remediation detail is that JetBrains fixed the issue in TeamCity 2018.2.3.

Likely exposure

Exposure is most relevant to organizations running JetBrains TeamCity that had not updated to 2018.2.3 or later. The source bundle does not provide a precise vulnerable version range, deployment condition, affected page, or configuration requirement.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not marked as KEV. Stored JavaScript injection can matter when untrusted input is later rendered to other users, but this record lacks exploitability details and prerequisites.

Researcher notes

Useful missing details include the affected page, stored field, privilege requirement, sanitization failure, impacted version range, and whether user interaction is required. Validation should stay version-based unless JetBrains or internal testing provides safer, authorized checks.

Mitigation direction

  • Upgrade TeamCity to 2018.2.3 or later if still below that version.
  • Check JetBrains security guidance for any additional product-specific remediation.
  • Restrict administrative access to TeamCity while upgrade status is confirmed.
  • Review TeamCity exposure to the internet and limit access where feasible.

Validation and detection

  • Inventory TeamCity instances and record installed versions.
  • Confirm each instance is running TeamCity 2018.2.3 or later.
  • Review JetBrains bulletin details for CVE-2019-12844 applicability.
  • Check access controls for externally reachable TeamCity deployments.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-12844 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.