CVE-2010-2060 json
The put command functionality in beanstalkd 1.4.5 and earlier allows remote attackers to execute arbitrary Beanstalk commands via the body…
published 16y ago modified 4mo ago also EUVD-2010-2079
- cvss
- 7.5
- 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 put command functionality in beanstalkd 1.4.5 and earlier allows remote attackers to execute arbitrary Beanstalk commands via the body in a job that is too big, which is not properly handled by the dispatch_cmd function in prot.c.
Patch / fix
- beanstalkd Debian 14, Debian 13, Debian 12 1.4.6-1
debian advisories DEBIAN-CVE-2010-2060
Is CVE-2010-2060 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-2060 updated cvss 7.5
v1.4.6): Improper sanitization of job body (job payload data)
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
- github.com /kr/beanstalkd/commit/2e8e8c6387ecdf5923dfc4d7718d18eba1b0873d
-
secunia.com
/advisories/40032
third-party-advisory, vendor-advisory
- kr.github.com /beanstalkd/2010/05/23/1.4.6-release-notes.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59107
vdb-entry
-
osvdb.org
/65113
vdb-entry
-
securityfocus.com
/bid/40516
vdb-entry
Sources
- CVE List CVE-2010-2060
- NVD CVE-2010-2060
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.