LiveActive security incident?Get immediate response
CVE Record

CVE-2016-3704: Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.

Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Pulp versions before 2.8.5 generated some passwords using Bash $RANDOM, which is not suitable for security-sensitive secrets. This may leave credentials weaker than expected. The sources do not provide CVSS, confirmed exploitation, or detailed impact boundaries.

Executive priority

Treat as a targeted remediation item for legacy Pulp environments. It is not currently evidenced as actively exploited, but weak secret generation can undermine trust in authentication material if old generated credentials remain in use.

Technical view

CVE-2016-3704 concerns unsafe password generation in Pulp before 2.8.5. The referenced script used Bash $RANDOM in pulp-qpid-ssl-cfg, reducing unpredictability for generated passwords. Vendor and project references point to Pulp 2.8.5 and downstream advisories as remediation sources.

Likely exposure

Exposure is most likely on systems running Pulp before 2.8.5, especially where the referenced Qpid SSL configuration script generated credentials. Source data does not identify all affected packages, deployment modes, or reachable attack paths.

Exploitation context

The bundle does not cite active exploitation, and the CVE is not marked KEV. Practical risk depends on whether weakly generated passwords remain in use and whether an attacker can benefit from predicting or recovering them.

Researcher notes

Evidence is limited to the CVE description, Pulp release notes, issue tracker, script references, and vendor advisories. No CVSS, CWE, exploit status, or full affected-product matrix is included in the bundle.

Mitigation direction

  • Upgrade affected Pulp deployments to 2.8.5 or later.
  • Apply relevant Red Hat or Fedora fixed packages where applicable.
  • Review vendor guidance for credential or certificate rotation needs.
  • Prioritize systems where generated secrets are still trusted.

Validation and detection

  • Inventory Pulp versions and flag anything before 2.8.5.
  • Check whether pulp-qpid-ssl-cfg was used to generate operational secrets.
  • Confirm vendor fixed packages are installed on managed systems.
  • Review exposed services that rely on affected generated credentials.
Prepared
Confidence
medium
Sources
9

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.

cve · low confidence lookup

CVE-2016-3704 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
7Source 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/an/an/aListed
Weakness

CWE details

No CWE listed

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