Enterprise MrgOperating system · Redhat
CVE-2012-2684
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple SQL injection vulnerabilities in the get_sample_filters_by_signature function in Cumin before 0.1.5444, as used in Red Hat Enterprise Messaging, Realtime, and Grid (MRG) 2.0, allow remote attackers to execute arbitrary SQL commands via the (1) agent or (2) object id.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in Cumin's get_sample_filters_by_signature function allows remote attackers to inject arbitrary SQL commands via unsanitized 'agent' and 'object id' parameters. The function directly incorporates user-supplied input into SQL queries without proper parameterization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise MrgOperating system
= 2.0<= 0.1.5192-4= 0.1.3160-1= 0.1.4369-1= 0.1.4410-2= 0.1.4494-1= 0.1.4794-1= 0.1.4916-1= 0.1.5033-1= 0.1.5037-1= 0.1.5054-1= 0.1.5068-1= 0.1.5092-1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Cumin installation and versionRun 'rpm -q cumin' or check the installed Cumin package version using your system's package managerAffected if The installed version matches one of the affected versions: 0.1.5192-4, 0.1.3160-1, 0.1.4369-1, 0.1.4410-2, 0.1.4494-1, 0.1.4794-1, 0.1.4916-1, 0.1.5033-1, 0.1.5037-1, 0.1.5054-1, 0.1.5068-1, 0.1.5092-1 or Redhat Enterprise Mrg 2.0
-
Locate the get_sample_filters_by_signature functionSearch the Cumin source code for the function 'get_sample_filters_by_signature' to confirm it exists in your installationAffected if The function exists in the codebase and directly incorporates user-supplied 'agent' and 'object id' parameters into SQL queries without parameterization
-
Determine if the vulnerable function is exposedReview Cumin web application or API configuration to check if endpoints calling get_sample_filters_by_signature are accessible to remote usersAffected if The function or its calling endpoints are accessible over the network without authentication or with authentication that can be bypassed
-
Verify user input reaches the vulnerable functionTest or review code to confirm that the 'agent' and 'object id' HTTP parameters are passed through to the get_sample_filters_by_signature function without sanitizationAffected if User-supplied input from HTTP requests can reach the SQL query without proper escaping or parameterized queries
You are affected if Cumin is installed with an affected version AND the get_sample_filters_by_signature function is exposed to remote users who can supply the 'agent' or 'object id' parameters.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Cumin to version 0.1.5444 or later. Until then, implement input validation and use parameterized queries for the affected function to prevent SQL injection.
Fix this in Enterprise Mrg
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-2684 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data