Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

org.apache.solr:solr-parent

Maven package

Overview

Newest range
8.11.1
Last CVE
23 Dec 2021
Maven 9 version ranges 8 affected
4 Critical
1 High
1 Medium
0 Low

Package versions

Version ranges and their known vulnerabilities
VersionsRangeDirect vulnerabilities
8.11.1 and later versions 0000
8.8.2 up to 8.11.1 1000
8.6.3 up to 8.8.2 3000
8.6.0 up to 8.6.3 4000
7.7.0 up to 8.6.0 4100
7.0.0 up to 7.7.0 4110
6.6.6 up to 7.0.0 4100
6.6.0 up to 6.6.6 4110
before 6.6.0 all earlier versions 3110

No known vulnerabilities in 8.11.1 and later versions

Nothing in our data affects this version.

9 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.

Vulnerabilities · 6

Known vulnerabilities of this package
CVESeverityPublishedVulnerableFixed in
CVE-2021-44548Apache Solr Improper Input Validation and Path Traversal CRITICAL 23 Dec 2021 <8.11.1 8.11.1
CVE-2021-29943solr: unprivileged users may be able to perform unauthorized read/write to collections CRITICAL 13 Apr 2021 <8.8.2 8.8.2
CVE-2021-27905solr: SSRF vulnerability with the Replication handler CRITICAL 13 Apr 2021 <8.8.2 8.8.2
CVE-2020-13957solr: The checks added to unauthenticated configset uploads can be circumvented CRITICAL 13 Oct 2020 >=6.6.0, <8.6.3 8.6.3
CVE-2020-13941solr: replication handler allows a read-write operations to any location the solr user can access HIGH 17 Aug 2020 <8.6.0 8.6.0
CVE-2018-11802solr: Information disclosure via Rule-base Authorization plugin MEDIUM 1 Apr 2020 >=7.0.0, <7.7.0<6.6.6 7.7.06.6.6

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.