First published: Mon May 02 2005(Updated: )
Unknown vulnerability in PaX from the September 2003 release to 2.2 before 2005.03.05, related to SEGMEXEC or RANDEXEC and VMA mirroring, allows local users and possibly remote attackers to bypass intended access restrictions and execute arbitrary code.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
The Pax Team Pax Linux | =2.4.23 | |
The Pax Team Pax Linux | =2.2 | |
The Pax Team Pax Linux | =2.4.27 | |
The Pax Team Pax Linux | =2.4.25 | |
The Pax Team Pax Linux | =2.6.5 | |
The Pax Team Pax Linux | =2.4.28 | |
The Pax Team Pax Linux | =2.4.24 | |
The Pax Team Pax Linux | =2.4.20 | |
The Pax Team Pax Linux | =2.4.22 | |
The Pax Team Pax Linux | =2.4.21 | |
The Pax Team Pax Linux | =2.4.26 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-0666 is considered a critical vulnerability due to its potential for arbitrary code execution.
To mitigate CVE-2005-0666, upgrade to a patched version of PaX that addresses this vulnerability.
CVE-2005-0666 affects PaX versions 2.2 through 2.4.28, prior to the fix released on 2005.03.05.
Yes, CVE-2005-0666 can potentially be exploited by remote attackers to bypass access restrictions.
Local users as well as remote attackers can be impacted by CVE-2005-0666 due to its nature of allowing arbitrary code execution.