LiveActive security incident?Get immediate response
CVE Record

CVE-2012-3460: cumin: At installation postgresql database user created without password

cumin: At installation postgresql database user created without password

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2012-3460 describes a Cumin installation flaw where a PostgreSQL database user was created without a password. That could leave management data exposed if PostgreSQL allowed that account to authenticate. The source bundle does not provide CVSS, active exploitation evidence, or a named fixed version.

Executive priority

Prioritize as a legacy exposure review, not an emergency based on current evidence. Escalate if Cumin is still in use, the database is reachable beyond localhost, or the passwordless account remains active.

Technical view

Affected Cumin versions through 2012-08-08 reportedly created a PostgreSQL database user with no password during installation. Practical impact depends on PostgreSQL authentication rules, host/network access, and whether the account still exists. No CWE, CVSS vector, patch version, or exploit details are provided in the supplied sources.

Likely exposure

Exposure is most likely on legacy Cumin deployments installed on or before 2012-08-08. Systems are higher risk if the passwordless PostgreSQL user remains present and database access is reachable locally or over a trusted network.

Exploitation context

The bundle does not indicate CISA KEV inclusion, active exploitation, public exploit code, or remote exploitability. This should be treated as a legacy configuration exposure until local account and PostgreSQL authentication state are verified.

Researcher notes

The evidence is sparse: no CVSS, CWE, exploit status, fixed version, or detailed advisory text is included. Focus validation on actual PostgreSQL role state and authentication paths rather than assuming universal remote exposure.

Mitigation direction

  • Check Red Hat or upstream Cumin guidance for supported remediation.
  • Inventory Cumin installations from 2012-08-08 or earlier.
  • Remove, disable, or set credentials for any passwordless PostgreSQL Cumin account.
  • Restrict PostgreSQL access to required hosts only.
  • Retire unsupported Cumin deployments where practical.

Validation and detection

  • Confirm whether Cumin is installed and identify its installation date or package version.
  • Review PostgreSQL roles for Cumin-related users without passwords.
  • Review PostgreSQL authentication policy for how that role can connect.
  • Check database listener exposure and host firewall rules.
  • Document whether vendor remediation guidance exists for the deployed package.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-3460 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
cumincuminthrough 2012-08-08Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.