Enterprise MrgOperating system · Redhat
CVE-2012-3460
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 · uneditedcumin: At installation postgresql database user created without password
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 · moderate confidenceDuring Cumin software installation, a PostgreSQL database user is created without a password, allowing unauthenticated remote attackers to gain full database access with the privileges of that user.
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.0CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify Cumin is installedRun 'rpm -qa | grep -i cumin' or check for Cumin installation directories under /usr/lib/cumin or similar locationsAffected if Cumin package is present on the system
-
Identify the Cumin PostgreSQL userCheck Cumin configuration files (typically in /etc/cumin/) for database connection settings, looking for the 'db_user' or 'user' parameter in cumin.conf or similar config filesAffected if A PostgreSQL username is defined for Cumin (commonly 'cumin' or 'cuminuser')
-
Examine pg_hba.conf for authentication methodLocate the PostgreSQL pg_hba.conf file (typically in /var/lib/pgsql/data/ or /etc/postgresql/) and check the authentication method specified for the Cumin database user's entryAffected if The authentication method is set to 'trust', 'ident', or 'md5' without a properly set password for the Cumin user
-
Test for passwordless database accessAttempt to connect to PostgreSQL using the Cumin database user without providing a password: 'psql -h <hostname> -U <cumin_user> -d <cumin_database>'Affected if Connection succeeds without requiring a password, indicating the user has no password set
-
Check PostgreSQL network listening configurationExamine postgresql.conf for 'listen_addresses' setting and verify if PostgreSQL is bound to a network-accessible IP address rather than localhost onlyAffected if listen_addresses is set to '*' or a public IP and pg_hba.conf permits non-local connections for the Cumin user
If Cumin is installed with a PostgreSQL database user accessible via network without password authentication (trust/ident method in pg_hba.conf), the environment is affected by this vulnerability.
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 dataImmediately set a strong password for the affected PostgreSQL database user and configure pg_hba.conf to enforce password authentication. Review database access logs for unauthorized activity.
Fix this in Enterprise Mrg
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3460 — 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-3460 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