vciy

CVE-2023-38152

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.

DHCP Server Service Information Disclosure Vulnerability

CVE-2023-381524 of 4 sources documented this
23

rank 23 = 6 + 13 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.25807  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from the CNA  ·  without this subject the record ranks 10

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 23

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$310,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$310,000 = $4.99M incident cost x 0.24048551839932833 exposure x 0.25807 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.25807EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 91 days at 0.26, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Microsoft Windows Server 2019? 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
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-126 Buffer Over-readreceipt
Published consequencesCWE-126: Confidentiality: Read Memory; Confidentiality: Bypass Protection Mechanism; Availability, Integrity: DoS: Crash, Exit, or Restart[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in10.0.17763.4851; 10.0.20348.1970; 10.0.14393.6252; 6.0.6003.22264; 6.1.7601.26713; 6.2.9200.24462; 6.3.9600.21563receipt
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 CNA5.3 MEDIUMreceipt
Exploit probability0.25807 · top 2% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes34 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows Server 2019; Microsoft Windows Server 2019 (Server Core installation); Microsoft Windows Server 2022; Microsoft Windows Server 2016…receipt
Published rangesmicrosoft windows server 2008 r2; microsoft windows server 2012 r2receipt
Fixed in10.0.17763.4851; 10.0.20348.1970; 10.0.14393.6252; 6.0.6003.22264; 6.1.7601.26713; 6.2.9200.24462; 6.3.9600.21563receipt

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.

What it is stated by the CNA

DHCP Server Service Information Disclosure Vulnerability receipt

NVD's analysis a second authority

weakness
CWE-126; CWE-668
affected versions
microsoft windows server 2008 r2; microsoft windows server 2012 r2
also scored by
[email protected] 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

check it yourself msrc.microsoft.com receipt

Movement the material steps

13 Sep 20230.00046
17 Mar 20250.01051 · scoring model v2025.03.14
15 Jun 20260.24014 · crossed 0.10 · scoring model v2026.06.15
14 Sep 20260.25807

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

Show all 34 observations
13 Sep 20230.00046
15 Sep 20230.00359
25 Nov 20230.00918
28 Dec 20230.01631
15 Jan 20240.01399
30 Jan 20240.01853
15 Feb 20240.01586
23 Feb 20240.01613
19 Mar 20240.01142
27 Mar 20240.01300
7 Apr 20240.00946
20 Apr 20240.00537
15 Jun 20240.00776
26 Jun 20240.00548
8 Jul 20240.00318
19 Jul 20240.00552
1 Aug 20240.00447
12 Aug 20240.00338
24 Aug 20240.01214
7 Sep 20240.00444
18 Sep 20240.00337
17 Dec 20240.00050
26 Jan 20250.00059
9 Feb 20250.00050
17 Mar 20250.01051
19 Mar 20250.00864
25 Mar 20250.01187
29 Mar 20250.04281
30 Mar 20250.01187
15 Apr 20250.0239
18 Nov 20250.01187
21 Nov 20250.0239
15 Jun 20260.24014
14 Sep 20260.25807

34 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.25807Published2023-09-12Index as of2026-09-14

Exploit probability more than doubled between 2023-09-13 and 2023-09-15 (0.00046 → 0.00359) and the record had been public for 3 years when this index was last written.

Published 2023-09-12 receipt · Index as of 2026-09-14 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft windows server 2019

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

Family membership: held values

Nothing we hold separates this record from the others in its defect family. 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-2023-38152.

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.