vciy

CVE-2024-23917

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible

CVE-2024-239174 of 4 sources documented this
41

rank 41 = 13 + 25 + 1 + 2 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.53730  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.8, from NVD  ·  without this subject the record ranks 16

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-03-26  ·  without this subject the record ranks 40

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 39

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 41

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.68Mover the next 30 days, if this record is yours
Movement-$1.30Mon 2026-02-24, the last material move, 4 months before this reading
Basisassumeda published average, not your estate

$2.68M = $4.99M incident cost x 1 exposure x 0.5373 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.5373EPSSNOT IN KEVas of 2026-09-20
Severity9.8 CRITICALreceipt
Harmtotal loss · unauthenticatedreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
RISING10Risen from 0.00043 to 0.5373 across 50 observations. arc-rules@v1

Foresight · where to check next

JetBrainsF5 BIG-IPSolarWinds OrionFortinet FortiOSFortinet FortiWeb23917

This record is one instance of CWE-288, authentication bypass using an alternate path or channel. The index holds 681 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running JetBrains TeamCity? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-288 Authentication Bypass Using an Alternate Path or Channelreceipt
Published consequencesCWE-288: Access Control: Bypass Protection Mechanism[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in2023.11.3receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA9.8 CRITICALreceipt
CVSS, NVD9.8 CRITICALreceipt
Exploit probability0.5373 · top 1% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byJetBrainsreceipt
Recorded changes50 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productJetBrains TeamCityreceipt
Published rangesjetbrains teamcity < 2023.11.3receipt
Fixed in2023.11.3receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Unauthenticated network requestno credentials, no interactionJetBrains TeamCityCWE-288 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-288data compromise

What it is stated by the CNA

In JetBrains TeamCity before 2023.11.3 authentication bypass leading to RCE was possible receipt

NVD's analysis a second authority

severity
9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-288; CWE-306
affected versions
jetbrains teamcity < 2023.11.3
also scored by
[email protected] 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

check it yourself jetbrains.com receipt

Dated events

2024-11-09EPSS moved 0.06 to 0.142025-03-17EPSS moved 0.43 to 0.942026-06-15EPSS moved 0.73 to 0.54

Movement the material steps

8 Feb 20240.00043
9 Nov 20240.14422 · crossed 0.10
17 Dec 20240.09423 · crossed 0.10
6 Jan 20250.11535 · crossed 0.10
1 Feb 20250.08489 · crossed 0.10
12 Feb 20250.12468 · crossed 0.10
14 Feb 20250.50305 · crossed 0.50
10 Mar 20250.42547 · crossed 0.50
17 Mar 20250.94335 · crossed 0.50 and 0.90 · scoring model v2025.03.14
24 Feb 20260.68322 · crossed 0.90
15 Jun 20260.54009 · scoring model v2026.06.15
28 Jun 20260.5373

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 50 observations
8 Feb 20240.00043
9 Feb 20240.00091
3 May 20240.04469
15 May 20240.05232
23 May 20240.04384
11 Jul 20240.04064
13 Aug 20240.04993
24 Sep 20240.05046
5 Oct 20240.05714
9 Nov 20240.14422
20 Nov 20240.16030
2 Dec 20240.12482
17 Dec 20240.09423
26 Dec 20240.09099
6 Jan 20250.11535
1 Feb 20250.08489
12 Feb 20250.12468
14 Feb 20250.50305
10 Mar 20250.42547
17 Mar 20250.94335
18 Mar 20250.94308
19 Mar 20250.9435
20 Mar 20250.94275
23 Mar 20250.94305
24 Mar 20250.94275
27 Mar 20250.94305
29 Mar 20250.94298
30 Mar 20250.94305
15 Apr 20250.94433
7 May 20250.94416
21 May 20250.94417
28 Jun 20250.94377
30 Jul 20250.94299
1 Oct 20250.94417
27 Oct 20250.94299
28 Oct 20250.94417
13 Nov 20250.94377
18 Nov 20250.94277
21 Nov 20250.94377
27 Dec 20250.94299
28 Dec 20250.94377
31 Dec 20250.94417
18 Feb 20260.94411
20 Feb 20260.9437
24 Feb 20260.68322
10 Mar 20260.69434
16 Mar 20260.68322
26 Mar 20260.72925
15 Jun 20260.54009
28 Jun 20260.5373

50 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.5373Published2024-02-06Index as of2026-06-28

Exploit probability more than doubled between 2024-02-08 and 2024-02-09 (0.00043 → 0.00091) and the record had been public for 2 years, 4 months when this index was last written.

Published 2024-02-06 receipt · Index as of 2026-06-28 derived

The pattern, elsewhere

This record is one instance of CWE-288, authentication bypass using an alternate path or channel. The index holds 681 prior instances of this class, 20 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2023-42793 · JetBrains TeamCitymatches 10 of 10KEV listed · 2023receipt
CVE-2024-27198 · JetBrains TeamCitymatches 9 of 10KEV listed · 2024receipt
CVE-2023-46747 · F5 BIG-IPmatches 9 of 10KEV listed · 2023receipt
CVE-2020-10148 · SolarWinds Orion Platformmatches 9 of 10KEV listed · 2020receipt
CVE-2024-55591 · Fortinet FortiOSmatches 8 of 10KEV listed · 2025receipt
CVE-2026-24858 · Fortinet FortiWebmatches 8 of 10KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

681 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

jetbrains teamcity

Of the 4 records in this family, this is the only one holding a stated fix version: 2023.11.3.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-23917.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.