dbcve.org
SolrApplication · Apache

CVE-2018-1308

HIGH · 7.5 CVSS v3.0 Published 2018-04-09
Fix available
A fix is available. Upgrade to after 7.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability in Apache Solr 1.2 to 6.6.2 and 7.0.0 to 7.2.1 relates to an XML external entity expansion (XXE) in the `&dataConfig=<inlinexml>` parameter of Solr's DataImportHandler. It can be used as XXE using file/ftp/http protocols in order to read arbitrary local files from the Solr server or the internal network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an XXE (XML External Entity) injection vulnerability in Apache Solr's DataImportHandler. Attackers can exploit the dataConfig parameter by injecting malicious XML containing external entity references (file://, ftp://, http:// protocols) to read arbitrary local files from the Solr server or probe internal network resources.

MitigationUpgrade to Solr 6.6.3 or 7.3.0+ which contain the security fix, or disable the DataImportHandler if not required in your deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SolrApplication
Affected:>= 1.2, <= 6.6.2>= 7.0.0, <= 7.2.1
Debian LinuxOperating system
Affected:= 7.0= 8.0= 9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Apache Solr version
    Run 'bin/solr version' from the Solr installation directory, or check the solr-core JAR manifest, or query the Solr admin API endpoint /solr/admin/info/system
    Affected if Version falls within 1.2 to 6.6.2 inclusive, or 7.0.0 to 7.2.1 inclusive
  2. Verify DataImportHandler is enabled
    Check for the presence of the DataImportHandler JAR (solr-dataimporthandler-*.jar) in the lib folder, and look for a requestHandler definition with name='/dataimport' in solrconfig.xml
    Affected if DataImportHandler JAR exists and a corresponding request handler is configured in solrconfig.xml
  3. Confirm dataConfig parameter is exposed
    Review solrconfig.xml for a requestHandler pointing to DataImportHandler and ensure it allows the 'dataConfig' parameter, or test by sending a request to /solr/{core}/dataimport with an empty dataConfig parameter
    Affected if The DataImportHandler request handler accepts the dataConfig parameter without strict validation
  4. Check Solr network exposure
    Examine the Solr service bind address in solr.in.sh or solr.in.cmd (property SOLR_HOST) and verify firewall rules or cloud provider security groups restricting access to port 8983
    Affected if Solr is bound to a public IP or accessible from untrusted networks without authentication
  5. Look for evidence of exploitation attempts
    Search Solr logs (in logs/solr.log) for patterns such as 'dataConfig' parameter containing 'DOCTYPE', 'ENTITY', or 'file://' strings, or review access logs for suspicious dataimport requests
    Affected if Logs contain XXE payload patterns in dataConfig parameter requests

You are affected if your Solr version is between 1.2 and 6.6.2 or between 7.0.0 and 7.2.1 AND the DataImportHandler is enabled and accessible with the dataConfig parameter exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.2.1
Interim mitigation

Upgrade to Solr 6.6.3 or 7.3.0+ which contain the security fix, or disable the DataImportHandler if not required in your deployment.

Fix this in Solr Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1308 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data