CVSS 3.0
7.8 highCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in apache spark. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.spark:spark-core_2.11 2.1.2.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Horg.apache.spark:spark-core_2.11 (Maven): fixed in 2.1.2org.apache.spark:spark-core_2.10 (Maven): fixed in 2.1.2pyspark (PyPI): fixed in 2.1.2Explain CVE-2017-12612 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-12612?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-12612?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-12612 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| apache:spark | 1.6.0 |
| apache:spark | 1.6.1 |
| apache:spark | 1.6.2 |
| apache:spark | 1.6.3 |
| apache:spark | 2.0.0 |
| apache:spark | 2.0.1 |
| apache:spark | 2.0.2 |
| apache:spark | 2.1.0 |
| apache:spark | 2.1.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-8rhc-48pp-52gr | Maven | org.apache.spark:spark-core_2.11 | <2.1.2 | 2.1.2 |
| GHSA-8rhc-48pp-52gr | Maven | org.apache.spark:spark-core_2.10 | <2.1.2 | 2.1.2 |
| GHSA-8rhc-48pp-52gr | PyPI | pyspark | <2.1.2 | 2.1.2 |
| PYSEC-2017-147 | PyPI | pyspark | <2.1.2 | 2.1.2 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.