BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2017
CVE-2017-12629High confidence

Elasticsearch, although it uses Lucene, is NOT vulnerable to this

Unknown · Apache Solr before 7.1 with Apache Lucene before 7.1

Official source article: Red Hat RHSA-2017:3451 ↗. Check the applicable product and release in the original source.

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 91.90% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Apache Solr before 7.1 with Apache Lucene before 7.1 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelucene-solrVendor fix publishedDebian records a fixed source-package version for this release.3.6.2+dfsg-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelucene-solrVendor fix publishedDebian records a fixed source-package version for this release.3.6.2+dfsg-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelucene-solrVendor fix publishedDebian records a fixed source-package version for this release.3.6.2+dfsg-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelucene-solrVendor fix publishedDebian records a fixed source-package version for this release.3.6.2+dfsg-11Debian Security Tracker ↗Source updated 5 Oct 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2018-0640

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

What

Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Remote code execution occurs in Apache Solr before 7.1 with Apache Lucene before 7.1 by exploiting XXE in conjunction with use of a Config API add-listener command to reach the RunExecutableListener class. Elasticsearch, although it uses Lucene, is NOT vulnerable to this. Note that the XML external entity expansion vulnerability occurs in the XML Query Parser which is available, by default, for any query request with parameters deftype=xmlparser and can be exploited to upload malicious data to the /upload request handler or as Blind XXE using ftp wrapper in order to read arbitrary local files from the Solr server. Note also that the second vulnerability relates to remote code execution using the RunExecutableListener available on all affected versions of Solr.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Restriction of XML External Entity Reference → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-611 ↗

CWE-611: Improper Restriction of XML External Entity Reference. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-611Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2016-0694 Référence CVE CVE-2016-1000027 https://www.cve.org/CVERecord?id=CVE-2016-1000027 Référence CVE CVE-2016-2149 https://www.cve.org/CVERecord?id=CVE-2016-2149 Référence CVE CVE-2016-2160 https://www.cve.org/CVERecord?id=CVE-2016-2160 Référence CVE CVE-2016-2781 https://www.cve.org/CVERecord?id=CVE-2016-2781 Référence CVE CVE-2016-3418 https://www.cve.org/CVERecord?id=CVE-2016-3418 Référence CVE CVE-2017-10140 https://www.cve.org/CVERecord?id=CVE-2017-10140 Référence CVE CVE-2017-11164 https://www.cve.org/CVERecord?id=CVE-2017-11164 Référence CVE CVE-2017-12195 https://www.cve.org/CVERecord?id=CVE-2017-12195 Référence CVE CVE-2017-12629 https://www.cve.org/CVERecord?id=CVE-2017-12629 Référence CVE CVE-2017-3604 https://www.cve.org/CVERecord?id=CVE-2017-3604 Référence CVE CVE-2017-3605 https://www.cve.org/CVERecord?id=CVE-2017-3605 Référence CVE CVE-2017-3606 https://www.cve.org/CVERecord?id=CVE-2017-3606 Référence CVE CVE-2017-3607 https://www.cve.org/CVERecord?id=CVE-2017-3607 Référence CVE CVE-2017-3608 https://www.cve.org/CVERecord?id=CVE-2017-3608 Référence CVE CVE-2017-3609 https://www.cve.org/CVERecord?id=CVE-2017-3609 Référence CVE CVE-2017-3610 https://www.cve.org/CVERecord?id=CVE-2017-3610 Référence CVE CVE-2017-3611 https://www.cve.org/CVERecord?id=CVE-2017-3611 R

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-009483Apache Lucene の Apache Solr における XML 外部エンティティの脆弱性

Apache Lucene の Apache Solr には、XML 外部エンティティの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Apache Solr before 7.1 with Apache Lucene before 7.1: Apache Solr before 7.1 with Apache Lucene before 7.1, lucene-solr < 7.1.0, lucene-solr < 5.3.1-redhat-2
Fixed
Apache Solr before 7.1 with Apache Lucene before 7.1: lucene-solr 7.2.0, lucene-solr 8.0.0
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 14 Oct 2017 · Last source change 5 Aug 2024, 18:43 UTC · CWE-611 · Improper Restriction of XML External Entity Reference

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2018-0640
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2018-0640 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2018-0640"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: mail-archives.us.apache.org/<CAOOKt51UO_6Vy=j8W=x1pMbLW9VJfZyFWz7pAnXJC_OAdSZubA@mail.gmail.com>; added vendor advisory: s.apache.org/FJDl; removed vendor advisory: access.redhat.com/RHSA-2017:3123; removed vendor advisory: access.redhat.com/RHSA-2017:3124; 9 further removals.
    Before
    remediation: access.redhat.com/RHSA-2017:3451 · vendor advisory: access.redhat.com/RHSA-2017:3123 · vendor advisory: access.redhat.com/RHSA-2017:3124 · 9 more references
    After
    remediation: access.redhat.com/RHSA-2017:3451 · vendor advisory: mail-archives.us.apache.org/<CAOOKt51UO_6Vy=j8W=x1pMbLW9VJfZyFWz7pAnXJC_OAdSZubA@mail.gmail.com> · vendor advisory: s.apache.org/FJDl
    access.redhat.com ↗
  3. Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
    Before
    Public exploit reference
    After
    Public exploit reference
    s.apache.org ↗
  4. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    NIST NVD ↗
  5. CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.8 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    NIST NVD ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2018-0640↗Public exploit reference↗Vendor advisory↗CVE authority or vendor reference · Red Hat RHSA-2017:3451↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2017-12629 · cve.blacktree.nl