CVE-2013-6883 json
Cross-site request forgery (CSRF) vulnerability in CRU Ditto Forensic FieldStation with firmware before 2013Oct15a allows remote attackers…
published 12y ago modified 4mo ago also EUVD-2013-6685
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site request forgery (CSRF) vulnerability in CRU Ditto Forensic FieldStation with firmware before 2013Oct15a allows remote attackers to hijack the authentication of administrators for requests that modify the disk erase technique settings via unspecified vectors.
Is CVE-2013-6883 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 FencerTimeline
- First public exploit (EDB-30396)
- Published
Exploit prediction
2.51% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-30396 Ditto Forensic FieldStation 2013Oct15a - Multiple Vulnerabilities webapps, 2013-12-17
- seclists.org http://seclists.org/fulldisclosure/2013/Dec/80 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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
-
exploit-db.com
/exploits/30396
exploit
-
seclists.org
/fulldisclosure/2013/Dec/80
mailing-list, exploit
-
secunia.com
/advisories/55989
third-party-advisory
- cru-inc.com /support/software-downloads/ditto-firmware-updates/ditto-firmware-release-notes-2013oct15a
- cru-inc.com /support/software-downloads/ditto-firmware-updates/ditto-firmware-release-notes-2013jun30a
- packetstormsecurity.com /files/124420/Ditto-Forensic-FieldStation-2013Oct15a-XSS-CSRF-Command-Execution.html
-
osvdb.org
/100999
vdb-entry
Sources
- CVE List CVE-2013-6883
- NVD CVE-2013-6883
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.