First published: Wed Feb 02 2011(Updated: )
MyProxy 5.0 through 5.2, as used in Globus Toolkit 5.0.0 through 5.0.2, does not properly verify the (1) hostname or (2) identity in the X.509 certificate for the myproxy-server, which allows remote attackers to spoof the server and conduct man-in-the-middle (MITM) attacks via a crafted certificate when executing (a) myproxy-logon or (b) myproxy-get-delegation.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
NCSA MyProxy | =5.0 | |
NCSA MyProxy | =5.1 | |
NCSA MyProxy | =5.2 | |
Globus Toolkit | =5.0.0 | |
Globus Toolkit | =5.0.1 | |
Globus Toolkit | =5.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-0738 is considered a medium severity vulnerability due to its potential for man-in-the-middle attacks.
To fix CVE-2011-0738, it is recommended to upgrade to a version of MyProxy newer than 5.2 or Globus Toolkit newer than 5.0.2.
CVE-2011-0738 affects MyProxy versions 5.0 to 5.2 and Globus Toolkit versions 5.0.0 to 5.0.2.
CVE-2011-0738 can enable remote attackers to spoof the myproxy-server and conduct man-in-the-middle (MITM) attacks.
CVE-2011-0738 involves improper verification of both the hostname and the identity in the X.509 certificate for the myproxy-server.