CVE-2013-7379 json
API Admin Auth Weakness in tomato
published 12y ago modified 4mo ago also GHSA-9vxc-g2jx-qj3p , EUVD-2020-0607
- 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
- 0
- none known
Summary
The admin API in the tomato module before 0.0.6 for Node.js does not properly check the access key when it is set to a string, which allows remote attackers to bypass authentication via a string in the access-key header that partially matches config.master.api.access_key.
Patch / fix
Is CVE-2013-7379 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
2.46% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/leizongmin/tomato/commit/9e427d524e04a905312a3294c85e939ed7d57b8c referenced PoC, tagged "exploit" by a source, unverified
- nodesecurity.io https://nodesecurity.io/advisories/Tomato_API_Admin_Auth_Weakness 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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | tomato | <0.0.6 |
0.0.6 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/leizongmin/tomato/commit/9e427d524e04a905312a3294c85e939ed7d57b8c
web, exploit, patch
-
nodesecurity.io
/advisories/Tomato_API_Admin_Auth_Weakness
exploit
-
openwall.com
/lists/oss-security/2014/05/15/2
mailing-list, web
-
openwall.com
/lists/oss-security/2014/05/13/1
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2013-7379
advisory
-
github.com
/leizongmin/tomato
package
-
npmjs.com
/advisories/38
web
Sources
- CVE List CVE-2013-7379
- GitHub Advisory GHSA-9vxc-g2jx-qj3p
- NVD CVE-2013-7379
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.