Digest · Monday

Security digest: March 4, 2024

2 editorial briefs, 1 known exploited (cisa kev) addition and 2 critical advisories.

All digests · RSS · Markdown

Take stock

  • Check exposure: TeamCity CVE-2024-27198: Auth Bypass Used by Ransomware. Owners of self-hosted TeamCity servers that ran 2023.11.3 or older without the security patch plugin at any point after March 4, 2024, especially internet-facing ones.
  • Check exposure: TeamCity CVE-2024-27199: Path Traversal Joins KEV in 2026. Owners of self-hosted TeamCity servers still on 2023.11.3 or older, servers patched only with the 2024 plugin, and anyone whose server was internet-facing and unpatched in early March 2024.
  • Do you run any of these? Microsoft Windows. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2024-03-25.
  • npm: 1 critical advisory (jsonata). Check with npm audit (or: npm ls <package>).
  • Go: 1 critical advisory (github.com/zeromicro/go-zero). Check with govulncheck ./....
  • None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.

Editorial briefs

Check exposure

· Vulnerability · CVE-2024-27198

TeamCity CVE-2024-27198: Auth Bypass Used by Ransomware

Any TeamCity server that was internet-reachable and below 2023.11.4 in March 2024 may have been taken over; upgrade to a current release (which also fixes 2026's CVE-2026-63077) and audit for rogue admins and plugins.

Must act: Owners of self-hosted TeamCity servers that ran 2023.11.3 or older without the security patch plugin at any point after March 4, 2024, especially internet-facing ones.

Can relax: TeamCity Cloud customers, whom JetBrains patched and says were not attacked, and on-prem servers that were patched promptly and are now on a current release.

  1. Check the TeamCity version on every self-hosted server (shown in the web UI footer and under Administration).
  2. Upgrade to a current TeamCity release; 2023.11.4 fixes this bug, but 2025.11.7 or 2026.1.3 and later are needed for 2026's CVE-2026-63077.
  3. Keep the TeamCity web UI off the internet or behind a VPN or SSO proxy.

Read the brief →

Check exposure

· Vulnerability · CVE-2024-27199

TeamCity CVE-2024-27199: Path Traversal Joins KEV in 2026

Fixed since March 2024 alongside a critical sibling; confirm no TeamCity server is still on 2023.11.3 or older, move everything to a build that also fixes CVE-2026-63077, and hunt on servers that were exposed and unpatched in March 2024.

Must act: Owners of self-hosted TeamCity servers still on 2023.11.3 or older, servers patched only with the 2024 plugin, and anyone whose server was internet-facing and unpatched in early March 2024.

Can relax: TeamCity Cloud customers, and on-prem teams that upgraded in March 2024, are now on 2025.11.7, 2026.1.3 or later, and do not expose the server publicly.

  1. Inventory every TeamCity On-Premises server and record its version from the web UI footer or GET /app/rest/server.
  2. Upgrade anything older than 2025.11.7 or 2026.1.3 to a current release; the 2024 patch plugin covers only the March 2024 bugs.
  3. Remove direct internet exposure: put TeamCity behind a VPN or an IP allowlist.

Read the brief →

Known exploited (CISA KEV) 1

Added to CISA’s catalog on this day: confirmed exploitation in the wild. Due date = CISA’s deadline for US federal agencies.

CVEProduct and flawCISA due
CVE-2024-21338Microsoft Windows
Microsoft Windows Kernel Exposed IOCTL with Insufficient Access Control Vulnerability Ransomware
2024-03-25

Critical advisories by ecosystem 2

GitHub-reviewed advisories rated critical, published this day (Pacific time).

Go 1

Check: govulncheck ./...

npm 1

Check: npm audit (or: npm ls <package>)