CVE-2012-2251 json
rssh 2.3.2, as used by Debian, Fedora, and others, when the rsync protocol is enabled, allows local users to bypass intended restricted she…
published 2013-01-11 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2244
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
rssh 2.3.2, as used by Debian, Fedora, and others, when the rsync protocol is enabled, allows local users to bypass intended restricted shell access via a (1) "-e" or (2) "--" command line option.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-2251 updated cvss 6.5
rssh: bypass of rsync -e option filtering
-
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
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
debian.org
/security/2012/dsa-2578
vendor-advisory
-
secunia.com
/advisories/51307
third-party-advisory, vendor-advisory
-
openwall.com
/lists/oss-security/2012/11/27/15
mailing-list
-
securityfocus.com
/bid/56708
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/80334
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=877279
-
archives.neohapsis.com
/archives/bugtraq/2012-11/0101.html
mailing-list
Sources
- CVE List CVE-2012-2251
- NVD CVE-2012-2251
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.