Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2012-3491

condor: local users can abort any idle jobs

Overview

Published
28 Sep 2012
Modified
29 Apr 2026
Medium CVE
0 Registry packages
58 OS packages
3 Linux distributions
Yes Fix available

Description

src/condor_schedd.V6/schedd.cpp in Condor 7.6.x before 7.6.10 and 7.8.x before 7.8.4 does not properly check the permissions of jobs, which allows remote authenticated users to remove arbitrary idle jobs via unspecified vectors.

Source: OX vulnerability database

Severity

4 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:S/C:N/I:N/A:P

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 34 fixes

Red Hat 1 release · 31 packages

fixed 31
cumin rubygem-eventmachine python-wallaby rubygem-fssm rubygem-rack-accept deltacloud-core +25
Red Hat fixes for CVE-2012-3491
ReleasePackageFixed inAdvisory
cumin 0:0.1.5444-3.el6 RHSA-2012:1281
rubygem-eventmachine 0:0.12.10-7.el6 RHSA-2012:1281
python-wallaby +3 0:0.12.5-10.el6 RHSA-2012:1281
rubygem-fssm 0:0.2.7-1.el6 RHSA-2012:1281
rubygem-rack-accept +1 0:0.4.3-6.el6_0 RHSA-2012:1281
deltacloud-core +2 0:0.5.0-10.el6_2 RHSA-2012:1281

25 more rows

debian 2 releases · 1 package

fixed 2
condor
debian fixes for CVE-2012-3491
ReleasePackageFixed in
13 condor 7.8.2~dfsg.1-1+deb7u1
14 condor 7.8.2~dfsg.1-1+deb7u1

echo 1 release · 1 package

fixed 1
condor
echo fixes for CVE-2012-3491
ReleasePackageFixed in
condor 7.8.2~dfsg.1-1+deb7u1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.