ubuntu-cve-2017-3163
Vulnerability from osv_ubuntu
Published
2017-08-30 14:29
Modified
2025-09-08 16:44
Summary
Details
When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.
Severity
7.5 (High)
N/A (UNKNOWN)
References
{
"affected": [
{
"ecosystem_specific": {
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "liblucene3-contrib-java",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
},
{
"binary_name": "liblucene3-java",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
},
{
"binary_name": "libsolr-java",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
},
{
"binary_name": "solr-common",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
},
{
"binary_name": "solr-jetty",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
},
{
"binary_name": "solr-tomcat",
"binary_version": "3.6.2+dfsg-2ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:14.04:LTS",
"name": "lucene-solr",
"purl": "pkg:deb/ubuntu/lucene-solr@3.6.2+dfsg-2ubuntu0.1~esm2?arch=source\u0026distro=trusty/esm"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.6.2+dfsg-2ubuntu0.1~esm2"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.6.2+dfsg-1",
"3.6.2+dfsg-2",
"3.6.2+dfsg-2ubuntu0.1~esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "liblucene3-contrib-java",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
},
{
"binary_name": "liblucene3-java",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
},
{
"binary_name": "libsolr-java",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
},
{
"binary_name": "solr-common",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
},
{
"binary_name": "solr-jetty",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
},
{
"binary_name": "solr-tomcat",
"binary_version": "3.6.2+dfsg-8ubuntu0.1+esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:16.04:LTS",
"name": "lucene-solr",
"purl": "pkg:deb/ubuntu/lucene-solr@3.6.2+dfsg-8ubuntu0.1+esm1?arch=source\u0026distro=esm-apps/xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.6.2+dfsg-7",
"3.6.2+dfsg-8",
"3.6.2+dfsg-8ubuntu0.1",
"3.6.2+dfsg-8ubuntu0.1+esm1"
]
}
],
"aliases": [],
"details": "When using the Index Replication feature, Apache Solr nodes can pull index files from a master/leader node using an HTTP API which accepts a file name. However, Solr before 5.5.4 and 6.x before 6.4.1 did not validate the file name, hence it was possible to craft a special request involving path traversal, leaving any file readable to the Solr server process exposed. Solr servers protected and restricted by firewall rules and/or authentication would not be at risk since only trusted clients and users would gain direct HTTP access.",
"id": "UBUNTU-CVE-2017-3163",
"modified": "2025-09-08T16:44:04Z",
"published": "2017-08-30T14:29:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2017-3163"
},
{
"type": "REPORT",
"url": "https://issues.apache.org/jira/browse/SOLR-10031"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2017-3163"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2017-3163"
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…