How severe is CVE-2013-7379?

No CVSS score has been assigned to CVE-2013-7379 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-7379?

CVE-2013-7379 affects the following packages: tomato (npm). Ecosystems affected: npm.

How do I fix CVE-2013-7379?

Update tomato to 0.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7379 is resolved across your whole dependency graph.

How do I detect CVE-2013-7379 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tomato, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-7379 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2013-7379 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2013-7379, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-7379?

CVE-2013-7379 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-7379?

CVE-2013-7379 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-7379 published, and has it been updated?

CVE-2013-7379 was published on August 31, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2013-7379 — tomato

Fix: leizongmin/tomato@9e427d5

CVE-2013-7379 is a Improper Authentication vulnerability in tomato. 2 public exploit references exist, so weaponization risk is real. A fix is available for tomato — see the affected versions and patch details below.

API Admin Auth Weakness in tomato

Published

Aug 31, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

tomatonpm

54downloads / week

Description

Versions of tomato prior to 0.0.6 are affected by a somewhat complex authentication bypass vulnerability in the admin service when only a single access key is configured on the server. The vulnerability allows an attacker to guess the password for the admin service, no matter how complex that password is, in less than 200 requests.

Details

The tomato API has an admin service that is enabled by setting up an access_key in the config options. This access_key is intended to protect the API admin from unauthorized access.

Tomato verifies the access_key by checking to see if the server access_key incorporates the user provided value at any location. This allows an attacker to provide a single character as an access_key, and so long as the server key contains at least one instance of that character it will be considered a valid key.

Proof of Concept

This is the snippet of code that does the comparison to authorize requests.

if (access_key && config.master.api.access_key.indexOf(access_key) !== -1) {

For an access_key that is set to anything that includes the letter 'a' the following request would be authorized.

$ curl -X POST "http://localhost:8081/api/exec" -H "Content-Type: application/json" -d @test -H "access-key: a"
{
 "cmd": "ls",
 "path": ".",
 "stdout": "app.js\nconfig.js\nlog\nnode_modules\nserver.js\n",
 "stderr": ""
}

Recommendation

Update to version 0.0.6 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`tomato`	all versions	0.0.6`npm install tomato@0.0.6`

Affected Products

1 product · 1 configurations

Application

tomatoucdok

≤ 0.0.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The admin API in the tomato module before 0.0.6 for Node.js does not pro…

github.comNVDMay 2014

The admin API in the tomato module before 0.0.6 for Node.js does not pro…

nodesecurity.ioNVDMay 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tomato, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tomato to 0.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-7379 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Versions of `tomato` prior to 0.0.6 are affected by a somewhat complex authentication bypass vulnerability in the admin service when only a single access key is configured on the server. The vulnerability allows an attacker to guess the password for the admin service, no matter how complex that password is, in less than 200 requests. ## Details The tomato API has an admin service that is enabled by setting up an `access_key` in the config options. This `access_key` is intended to protect the API admin from unauthorized access. Tomato verifies the `access_key` by checking to see if the serv

O3 Security · Impact-Aware SCA

Is CVE-2013-7379 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works