First published: Tue Aug 14 2012(Updated: )
Florian Weimer of the Red Hat Product Security Team found that an unauthenticated user able to connect to the Condor startd TCP port could request ads, provided they could guess or brute force the PID of the process, due to how the GIVE_REQUEST_AD handler is registered. The ads contains a lot of already-public information for users with READ privileges, however it also provides the ClaimId (as opposed to the PublicClaimId which truncates the full value of the ClaimID). If an attacker could obtain the private ClaimId, they could use it to control the running job, and also start new jobs on the system.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Condor Project Condor | =7.6.0 | |
Condor Project Condor | =7.6.1 | |
Condor Project Condor | =7.6.2 | |
Condor Project Condor | =7.6.3 | |
Condor Project Condor | =7.6.4 | |
Condor Project Condor | =7.6.5 | |
Condor Project Condor | =7.6.6 | |
Condor Project Condor | =7.6.7 | |
Condor Project Condor | =7.6.8 | |
Condor Project Condor | =7.6.9 | |
Condor Project Condor | =7.8.0 | |
Condor Project Condor | =7.8.1 | |
Condor Project Condor | =7.8.2 | |
Condor Project Condor | =7.8.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.