CVE-2018-11802: Incorrect Authorization in Apache Solr

CVE-2018-11802 · Severity: low · CVSS 3.1 · Published 2022-02-09

Incorrect Authorization in Apache Solr

Technologies: org.apache.solr:solr-core (Maven), org.apache.solr:solr-parent (Maven). Vendors: Maven.

Quick answers

Is CVE-2018-11802 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-11802 being exploited in the wild.
How severe is CVE-2018-11802?
Low severity, with a CVSS score of 3.1, published 9 February 2022.
Which products and versions are affected?
org.apache.solr:solr-core (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.7.0; org.apache.solr:solr-parent (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.7.0.
Is there a fix for CVE-2018-11802?
Yes. org.apache.solr:solr-core (Maven): upgrade to 7.7.0 or later; org.apache.solr:solr-parent (Maven): upgrade to 7.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-11802?
Check whether you run org.apache.solr:solr-core (Maven) or org.apache.solr:solr-parent (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.solr:solr-core (Maven): upgrade to 7.7.0 or later
    # set org.apache.solr:solr-core to 7.7.0 in your pom.xml or build.gradle
  • org.apache.solr:solr-parent (Maven): upgrade to 7.7.0 or later
    # set org.apache.solr:solr-parent to 7.7.0 in your pom.xml or build.gradle

Affected products

  • org.apache.solr:solr-core (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.7.0
  • org.apache.solr:solr-parent (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.7.0

Identifiers

  • CVE-2018-11802
  • GHSA-j346-h5wc-rw2m

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.