CVE-2012-2734: Multiple cross-site request forgery (CSRF) vulnerabilities in Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and…
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.91% (FIRST EPSS); higher than 60.7% of all records.
- Fixed version: condor (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5; condor-aviary (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5; condor-classads (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5.
Low priority for now. Upgrade to condor (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5; condor-aviary (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5; condor-classads (Red Hat:enterprise_mrg:2::el5) 0:7.6.5-0.22.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple cross-site request forgery (CSRF) vulnerabilities in Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, allow remote attackers to hijack the authentication of arbitrary users for requests that execute commands via unspecified vectors.
- Published
- Sep 28, 2012
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 60th percentile
- CWE
- CWE-352
Report tools
Action score
27
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| trevor mckay | cumin | cpe:2.3:a:trevor_mckay:cumin |
| redhat | enterprise mrg | cpe:2.3:o:redhat:enterprise_mrg |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat enterprise mrg2.0
- trevor mckay cuminup to 0.1.5192-4 inclusive
- trevor mckay cumin0.1.3160-1
- trevor mckay cumin0.1.4369-1
- trevor mckay cumin0.1.4410-2
- trevor mckay cumin0.1.4494-1
- trevor mckay cumin0.1.4794-1
- trevor mckay cumin0.1.4916-1
+12 more rows
- trevor mckay cumin0.1.5033-1
- trevor mckay cumin0.1.5037-1
- trevor mckay cumin0.1.5054-1
- trevor mckay cumin0.1.5068-1
- trevor mckay cumin0.1.5092-1
- trevor mckay cumin0.1.5098-2
- trevor mckay cumin0.1.5105-1
- trevor mckay cumin0.1.5137-1
- trevor mckay cumin0.1.5137-2
- trevor mckay cumin0.1.5137-3
- trevor mckay cumin0.1.5137-4
- trevor mckay cumin0.1.5137-5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_mrg:2::el5 | condor | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-aviary | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-classads | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-debuginfo | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-kbdd | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-qmf | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-vm-gahp | before 0:7.6.5-0.22.el5 | 0:7.6.5-0.22.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-wallaby | before 0:4.1.3-1.el5 | 0:4.1.3-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-wallaby-base-db | before 0:1.23-1.el5 | 0:1.23-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-wallaby-client | before 0:4.1.3-1.el5 | 0:4.1.3-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | condor-wallaby-tools | before 0:4.1.3-1.el5 | 0:4.1.3-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | cumin | before 0:0.1.5444-3.el5 | 0:0.1.5444-3.el5 |
| Red Hat:enterprise_mrg:2::el5 | python-wallaby | before 0:0.12.5-10.el5 | 0:0.12.5-10.el5 |
| Red Hat:enterprise_mrg:2::el5 | python-wallabyclient | before 0:4.1.3-1.el5 | 0:4.1.3-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | ruby-wallaby | before 0:0.12.5-10.el5 | 0:0.12.5-10.el5 |
| Red Hat:enterprise_mrg:2::el5 | sesame | before 0:1.0-4.el5 | 0:1.0-4.el5 |
| Red Hat:enterprise_mrg:2::el5 | sesame-debuginfo | before 0:1.0-4.el5 | 0:1.0-4.el5 |
| Red Hat:enterprise_mrg:2::el5 | wallaby | before 0:0.12.5-10.el5 | 0:0.12.5-10.el5 |
| Red Hat:enterprise_mrg:2::el5 | wallaby-utils | before 0:0.12.5-10.el5 | 0:0.12.5-10.el5 |
| Red Hat:enterprise_mrg:2:computenode:el6 | condor | before 0:7.6.5-0.22.el6 | 0:7.6.5-0.22.el6 |
| Red Hat:enterprise_mrg:2:computenode:el6 | condor-classads | before 0:7.6.5-0.22.el6 | 0:7.6.5-0.22.el6 |
| Red Hat:enterprise_mrg:2:computenode:el6 | condor-debuginfo | before 0:7.6.5-0.22.el6 | 0:7.6.5-0.22.el6 |
| Red Hat:enterprise_mrg:2:computenode:el6 | condor-kbdd | before 0:7.6.5-0.22.el6 | 0:7.6.5-0.22.el6 |
| Red Hat:enterprise_mrg:2:computenode:el6 | condor-qmf | before 0:7.6.5-0.22.el6 | 0:7.6.5-0.22.el6 |
+62
Same product
trevor mckay: all recordsOther highest-scoring records for the same primary product.
- CVE-2012-2684Multiple SQL injection vulnerabilities in the get_sample_filters_by_signature function in Cumin before 0.1.5444, as used in Red Hat…31Monitor
- CVE-2012-2681Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, uses predictable random numbers to generate…24Monitor
- CVE-2012-2680Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, does not properly restrict access to…21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2012-2683Sep 28, 2012 · Multiple cross-site scripting (XSS) vulnerabilities in Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid…18Monitor
- ← EarlierCVE-2012-2685Sep 28, 2012 · Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, allows remote authenticated users to cause a…17Monitor
- Later →CVE-2012-2735Sep 28, 2012 · Session fixation vulnerability in Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, allows…19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:condor | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-aviary | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-classads | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-debuginfo | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-kbdd | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-qmf | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-vm-gahp | 0:7.6.5-0.22.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-wallaby | 0:4.1.3-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-wallaby-base-db | 0:1.23-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-wallaby-client | 0:4.1.3-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:condor-wallaby-tools | 0:4.1.3-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:cumin | 0:0.1.5444-3.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.