Skip to content

GHSA-vrh8-27q8-fr8f CVE-2017-3164

Server-Side Request Forgery (SSRF) in org.apache.solr:solr-core

High Maven
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
19.44%
Chance of exploitation in the next 30 days. Higher than 97.37% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-918 Server-Side Request Forgery (SSRF)
Fix
7.7.0
Upgrade org.apache.solr:solr-core to this version or later

Description

Server Side Request Forgery in Apache Solr, versions 1.3 until 7.6 (inclusive). Since the "shards" parameter does not have a corresponding whitelist mechanism, a remote attacker with access to the server could make Solr perform an HTTP GET request to any reachable URL.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.solr:solr-core
>= 1.3.0, < 7.7.0
7.7.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.solr:solr-core Maven → 7.7.0

maven
<dependency><groupId>org.apache.solr</groupId><artifactId>solr-core</artifactId><version>7.7.0</version></dependency>
gradle
implementation("org.apache.solr:solr-core:7.7.0")

Severity breakdown

CVSS 3.0 7.5

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

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

Weakness

CWE-918: Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2019-17558
Improper Input Validation in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
CVE-2019-0193
XML External Entity (XXE) Injection in Apache Solr
High Known exploited Also affects org.apache.solr:solr-core
GHSA-qhr7-h655-pw6r
Apache Solr has hardcoded credentials in the Basic Authentication setup tool
Critical Also affects org.apache.solr:solr-core
GHSA-vc2w-4v3p-2mqw
Apache Solr: Insufficient file-access checking in standalone core-creation requests
High Also affects org.apache.solr:solr-core
GHSA-qr3p-2xj2-q7hq
Apache Solr: Unauthorized bypass of certain "predefined permission" rules in the RuleBasedAuthorizationPlugin
High Also affects org.apache.solr:solr-core
GHSA-68r2-fwcg-qpm8
Apache Solr vulnerable to Execution with Unnecessary Privileges
Medium Also affects org.apache.solr:solr-core
GHSA-4p5m-gvpf-f3x5
Apache Solr Relative Path Traversal vulnerability
Medium Also affects org.apache.solr:solr-core
GHSA-37vr-vmg4-jwpw
Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets
High Also affects org.apache.solr:solr-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor