First published: Fri Mar 05 2010(Updated: )
Perforce Server 2009.2 and earlier, when the protection table is empty, allows remote authenticated users to obtain super privileges via a "p4 protect" command.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Perforce Helix Core | =2008.1 | |
Perforce Helix Core | =2007.3 | |
Perforce Helix Core | =2002.2 | |
Perforce Helix Core | =2000.2 | |
Perforce Helix Core | <=2009.2 | |
Perforce Helix Core | =2006.1 | |
Perforce Helix Core | =2001.2 | |
Perforce Helix Core | =99.2 | |
Perforce Helix Core | =2007.2 | |
Perforce Helix Core | =2004.2 | |
Perforce Helix Core | =2005.1 | |
Perforce Helix Core | =2005.2 | |
Perforce Helix Core | =2000.1 | |
Perforce Helix Core | =2001.1 | |
Perforce Helix Core | =2002.1 | |
Perforce Helix Core | =99.1 | |
Perforce Helix Core | =2007.3_143793 | |
Perforce Helix Core | =2003.1 | |
Perforce Helix Core | =97.3 | |
Perforce Helix Core | =2006.2 | |
Perforce Helix Core | =98.2 | |
Perforce Helix Core | =2003.2 | |
Perforce Helix Core | =2008.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-0935 has a medium severity rating as it allows remote authenticated users to gain super privileges.
To fix CVE-2010-0935, ensure that the protection table is properly configured to avoid granting super-user privileges.
CVE-2010-0935 affects Perforce Server versions up to and including 2009.2.
CVE-2010-0935 can lead to unauthorized access and manipulation of the server by granting super-user rights to authenticated users.
No, simply authenticating users is not sufficient; proper configuration of the protection table is necessary to mitigate CVE-2010-0935.