vciy

CVE-2023-50291

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.

Apache Solr: System Property redaction logic inconsistency can lead to leaked passwords

CVE-2023-502914 of 4 sources documented this
24

rank 24 = 1 + 19 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.03278  ·  without this subject the record ranks 23

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 5

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 24

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$100,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

$100,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.03278 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.03278EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2024-02-10, 903 days at 0.03, as of 2026-08-01. arc-rules@v1

Foresight · where to check next

CVE-2020-29583CVE-2017-9248RockwellCVE-2021-30116CVE-2014-181250291

This record is one instance of CWE-522, insufficiently protected credentials. The index holds 1501 prior instances of this class, 5 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 Apache Solr? 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 lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-522 Insufficiently Protected Credentialsreceipt
Published consequencesCWE-522: Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in9.3.0receipt
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, NVD7.5 HIGHreceipt
Exploit probability0.03278 · top 12% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byapachereceipt
Recorded changes27 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productApache Software Foundation Apache Solrreceipt
Published rangesapache solr >= 6.0.0 < 8.11.3; apache solr >= 9.0.0 < 9.3.0receipt
Fixed in9.3.0receipt

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

Insufficiently Protected Credentials vulnerability in Apache Solr. This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.3.0. One of the two endpoints that publishes the Solr process' Java system properties, /admin/info/properties, was only setup to hide system properties that had "password" contained in the name. There are a number of sensitive system properties, such as "basicauth" and "aws.secretKey" do not contain "password", thus their values were published via the "/admin/info/properties" endpoint. This endpoint populates the list of System Properties on the home screen of the Solr Admin page, making the exposed credentials visible in the UI. This /admin/info receipt

Read the rest of the CNA's description

/properties endpoint is protected under the "config-read" permission. Therefore, Solr Clouds with Authorization enabled will only be vulnerable through logged-in users that have the "config-read" permission. Users are recommended to upgrade to version 9.3.0 or 8.11.3, which fixes the issue. A single option now controls hiding Java system property for all endpoints, "-Dsolr.hiddenSysProps". By default all known sensitive properties are hidden (including "-Dbasicauth"), as well as any property with a name containing "secret" or "password". Users who cannot upgrade can also use the following Java system property to fix the issue:   '-Dsolr.redaction.system.pattern=.*(password|secret|basicauth).*'

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-522
affected versions
apache solr >= 6.0.0 < 8.11.3; apache solr >= 9.0.0 < 9.3.0
also scored by
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

check it yourself solr.apache.org openwall.com receipt

Movement the material steps

10 Feb 20240.00043
17 Mar 20250.00568 · scoring model v2025.03.14
15 Jun 20260.03306 · scoring model v2026.06.15
1 Aug 20260.03278
Show all 27 observations
10 Feb 20240.00043
16 Feb 20240.00079
13 Mar 20240.00112
17 Dec 20240.00223
15 Feb 20250.00341
28 Feb 20250.00337
13 Mar 20250.00256
17 Mar 20250.00568
29 Mar 20250.01906
30 Mar 20250.00568
15 Apr 20250.00274
22 Apr 20250.00282
5 May 20250.00274
19 Jun 20250.00414
30 Jun 20250.00562
16 Aug 20250.00578
26 Aug 20250.00562
10 Sep 20250.00372
18 Nov 20250.00637
21 Nov 20250.00372
22 Nov 20250.00498
18 Dec 20250.03176
23 Dec 20250.03093
21 Mar 20260.03157
26 Mar 20260.03074
15 Jun 20260.03306
1 Aug 20260.03278

27 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.03278Published2024-02-09Index as of2026-08-01

The record had been public for 2 years, 5 months when this index was last written.

Published 2024-02-09 receipt · Index as of 2026-08-01 derived

The pattern, elsewhere

This record is one instance of CWE-522, insufficiently protected credentials. The index holds 1501 prior instances of this class, 5 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2020-29583matches 6 of 8KEV listed · 2020receipt
CVE-2017-9248matches 6 of 8KEV listed · 2017receipt
CVE-2021-22681 · Rockwell Automation Studio 5000 Logix…matches 6 of 9KEV listed · 2021receipt
CVE-2021-30116matches 5 of 8KEV listed · 2021receipt
CVE-2014-1812nothing comparable heldKEV listed · 2014receipt

"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

1501 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

apache software foundation apache solr

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

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-2023-50291.

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.