CVE-2013-6618 in the critical feed json
jsdm/ajax/port.php in J-Web in Juniper Junos before 10.4R13, 11.4 before 11.4R7, 12.1 before 12.1R5, 12.2 before 12.2R3, and 12.3 before 12…
published 13y ago modified 4mo ago also EUVD-2013-6420
- cvss
- 9.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.6%
- EPSS 10.6% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
jsdm/ajax/port.php in J-Web in Juniper Junos before 10.4R13, 11.4 before 11.4R7, 12.1 before 12.1R5, 12.2 before 12.2R3, and 12.3 before 12.3R1 allows remote authenticated users to execute arbitrary commands via the rsargs parameter in an exec action.
Is CVE-2013-6618 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
- Published
- First public exploit (EDB-29544)
Exploit prediction
10.61% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-29544 Juniper Junos J-Web - Privilege Escalation webapps, 2013-11-12
- senseofsecurity.com.au http://www.senseofsecurity.com.au/advisories/SOS-13-003 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/62305 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
exploit-db.com
/exploits/29544
exploit
-
senseofsecurity.com.au
/advisories/SOS-13-003
exploit, url-repurposed
-
securityfocus.com
/bid/62305
vdb-entry, exploit
-
kb.juniper.net
/InfoCenter/index?page=content&id=JSA10560
vendor-advisory
-
secunia.com
/advisories/54731
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/87011
vdb-entry
-
securitytracker.com
/id/1029016
vdb-entry
Sources
- CVE List CVE-2013-6618
- NVD CVE-2013-6618
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.