First published: Wed Dec 28 2005(Updated: )
Argument injection vulnerability in scponlyc in scponly 4.1 and earlier, when both scp and rsync compatibility are enabled, allows local users to execute arbitrary applications via "getopt" style argument specifications, which are not filtered.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Scponly Scponly | =2.1 | |
Scponly Scponly | =3.5 | |
Scponly Scponly | =4.1 | |
Scponly Scponly | =3.0 | |
Scponly Scponly | =3.11 | |
Scponly Scponly | =2.0 | |
Scponly Scponly | =3.9 | |
Scponly Scponly | =3.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-4533 is considered a high-severity vulnerability due to the potential for local users to execute arbitrary applications.
To fix CVE-2005-4533, update scponly to version 4.2 or higher, where the argument injection vulnerability has been addressed.
CVE-2005-4533 affects local users of scponly versions 2.0 through 4.1 with both SCP and RSync compatibility enabled.
CVE-2005-4533 allows local users to manipulate command-line arguments and execute arbitrary applications.
No, CVE-2005-4533 only affects specific versions of Scponly, namely versions 2.0 to 4.1.