LiveActive security incident?Get immediate response
CVE Record

CVE-2014-0234: The default configuration of broker.conf in Red Hat OpenShift Enterprise 2.x before 2.1 has a password of "...

The default configuration of broker.conf in Red Hat OpenShift Enterprise 2.x before 2.1 has a password of "mooo" for a Mongo account, which allows remote attackers to hijack the broker by providing this password, related to the openshift.sh script in Openshift Extras before 20130920. NOTE: this may overlap CVE-2013-4253 and CVE-2013-4281.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Red Hat OpenShift Enterprise 2.x before 2.1 shipped with a known default Mongo account password in broker.conf. If that default remained in place and the broker was reachable, an attacker could take over broker control. This is legacy software risk, but high-impact where old OpenShift Enterprise deployments still exist. Exposure is most likely in legacy Red Hat OpenShift Enterprise 2.x environments, especially versions before 2.1, that retained default broker.conf credentials or old openshift-extras provisioning artifacts. Modern OpenShift versions are not identified as affected in the provided sources. Treat as high priority only where legacy OpenShift Enterprise 2.x still exists. The issue is old, but default credential exposure can turn an overlooked platform into direct administrative compromise. If no such systems remain, document non-exposure and close with asset evidence. Mitigation focus: Upgrade Red Hat OpenShift Enterprise 2.x systems to 2.1 or later per vendor guidance.; Review Red Hat advisory RHSA-2014-0487 for the vendor-provided correction path.; Remove any documented default Mongo credentials from broker.conf..

Prepared

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
cve · low confidence lookup

CVE-2014-0234 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
4Source 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
n/aRed Hat OpenShift Enterprise2.x before 2.1Listed
Weakness

CWE details

No CWE listed

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