API Admin Auth Weakness in tomato

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2013-7379: 2.46% estimated exploitation activity in the next 30 days; percentile 84.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 accesskey in the config options. This accesskey is intended to protect the API admin from unauthorized access. Tomato verifies the accesskey by checking to see if the server accesskey incorporates the user provided value at any location. This allows an attacker to provide a single character as an accesskey, 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. For an accesskey that is set to anything that includes the letter 'a'…

Published by the source

31 Aug 2020, 22:59 UTC

Last modified by the source

8 Nov 2023, 03:57 UTC

Source last checked

26 Oct 2026, 12:09 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9vxc-g2jx-qj3p

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9vxc-g2jx-qj3p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-7379

Advisory: API Admin Auth Weakness in tomato
IDs: CVE-2013-7379, GHSA-9vxc-g2jx-qj3p
Record: https://patchnext.com/advisories/cve-2013-7379 (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tomato 0.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tomato: affected <= 0.0.5; fixed in 0.0.6

## Suggested inspection (read-only)
- `npm ls tomato --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tomato.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9vxc-g2jx-qj3p (OSV record GHSA-9vxc-g2jx-qj3p lists affected ranges: npm tomato >=0 <0.0.6 (fixed))
- Verified: https://github.com/advisories/GHSA-9vxc-g2jx-qj3p (GitHub-reviewed advisory GHSA-9vxc-g2jx-qj3p lists affected ranges: npm tomato >=0 <=0.0.5)

Commands are suggestions: review each one before running it.