CVE-2018-1000206 json
JFrog Artifactory version since 5.11 contains a Cross ite Request Forgery (CSRF) vulnerability in UI rest endpoints that can result in Clas…
published 8y ago modified 4mo ago also EUVD-2018-1879
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 55%
- public exploits
- 0
- none known
Summary
JFrog Artifactory version since 5.11 contains a Cross ite Request Forgery (CSRF) vulnerability in UI rest endpoints that can result in Classic CSRF attack allowing an attacker to perform actions as logged in user. This attack appear to be exploitable via The victim must run maliciously crafted flash component. This vulnerability appears to have been fixed in 6.1.
Patch / fix
Is CVE-2018-1000206 in your stack? 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
0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- geekboy.ninja https://www.geekboy.ninja/blog/exploiting-json-cross-site-request-forgery-csrf-using-flash/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
jfrog.com
/jira/browse/RTFACT-17004
issue-tracking, patch, vendor-advisory
-
geekboy.ninja
/blog/exploiting-json-cross-site-request-forgery-csrf-using-flash/
exploit, third-party-advisory
-
jfrog.com
/jira/secure/ReleaseNote.jspa?projectId=10070&version=19581
release-notes, vendor-advisory
Sources
- CVE List CVE-2018-1000206
- NVD CVE-2018-1000206
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.