CVE-2017-12630 json
Apache Drill vulnerable to Cross-site Scripting
published 8y ago modified 4mo ago also GHSA-xp4g-5xj6-6vpr , EUVD-2022-5833
- cvss
- 5.4
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
In Apache Drill 1.11.0 and earlier when submitting form from Query page users are able to pass arbitrary script or HTML which will take effect on Profile page afterwards. Example: after submitting special script that returns cookie information from Query page, malicious user may obtain this information from Profile page afterwards.
Patch / fix
- maven org.apache.drill:drill-common 1.12.0
Is CVE-2017-12630 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| GitHub | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.drill:drill-common | <1.12.0 |
1.12.0 |
Affected products
- Apache Software Foundation Apache Drill
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
lists.apache.org
/thread.html/608658a55d09e16542db41121a0a972c97448214cdc04071fd4db923%40%3Cdev.drill.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2017-12630
advisory
-
github.com
/apache/drill
package
-
lists.apache.org
/thread.html/608658a55d09e16542db41121a0a972c97448214cdc04071fd4db923@%3Cdev.drill.apache.org%3E
web
Sources
- CVE List CVE-2017-12630
- GitHub Advisory GHSA-xp4g-5xj6-6vpr
- NVD CVE-2017-12630
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.