NVD / CVE Program· CNA apache

CVE-2024-45216: Apache Solr: Authentication bypass possible using a fake URL Path ending

Noroxi assessment

Priority: This week (action score 67/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 92.7% (FIRST EPSS); higher than 99.8% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Apache Software Foundation Apache Solr 8.11.4, 9.7.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Don’t wait for the next maintenance window. Upgrade to Apache Software Foundation Apache Solr 8.11.4, 9.7.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper Authentication vulnerability in Apache Solr. Solr instances using the PKIAuthenticationPlugin, which is enabled by default when Solr Authentication is used, are vulnerable to Authentication bypass. A fake ending at the end of any Solr API URL path, will allow requests to skip Authentication while maintaining the API contract with the original URL Path. This fake ending looks like an unprotected API path, however it is stripped off internally after authentication but before API routing. This issue affects Apache Solr: from 5.3.0 before 8.11.4, from 9.0.0 before 9.7.0. Users are recommended to upgrade to version 9.7.0, or 8.11.4, which fix the issue.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available

Published: Oct 16, 2024
Updated: Jun 17, 2026
EPSS: 92.7% · 99th percentile
CWE: CWE-287

Report tools

JSON

Action score

This week

Don’t wait for the next maintenance window.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 28 / 30 · 92.7%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	solr	cpe:2.3:a:apache:solr

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache solr5.3.0 and later · before 8.11.4
apache solr9.0.0 and later · before 9.7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache Solr
- 5.3.0 and later · before 8.11.4affected · semver
- 9.0.0 and later · before 9.7.0affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.apache.solr:solr	from 5.3.0 · before 8.11.4	8.11.4
Maven	org.apache.solr:solr	from 9.0.0 · before 9.7.0	9.7.0

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2019-17558Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter.KEV
90Now
CVE-2019-0193In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in whiKEV
83Now
CVE-2021-27905SSRF vulnerability with the Replication handler
67This week

Published before and after this one in the same product

← EarlierCVE-2023-50298Feb 9, 2024 · Apache Solr: Solr can expose ZooKeeper credentials via Streaming Expressions
30Monitor
← EarlierCVE-2023-50386Feb 9, 2024 · Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
60This week
Later →CVE-2024-45217Oct 16, 2024 · Apache Solr: ConfigSets created during a backup restore command are trusted implicitly
32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache Solr	8.11.4	Vendor (CNA)
Apache Software Foundation Apache Solr	9.7.0	Vendor (CNA)
Maven:org.apache.solr:solr	8.11.4	Package registry (OSV)
Maven:org.apache.solr:solr	9.7.0	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1
Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2024-45216	—
Proof-of-concept repository on GitHub	stars:2	2024-12-02

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 16, 2024
First PoCDec 2, 2024+47 d
TodayNov 7, 2026+753 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Liu Huajinreporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2024-52012103 days apartApache Solr: Configset upload on Windows allows arbitrary path write-access
35Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1715 · Oct 17, 2024(Apache Çoklu Ürün Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);