LiveActive security incident?Get immediate response
CVE Record

CVE-2016-3111: pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages...

pulp.spec in the installation process for Pulp 2.8.3 generates the RSA key pairs used to validate messages between the pulp server and pulp consumers in a directory that is world-readable before later modifying the permissions, which might allow local users to read the generated RSA keys via reading the key files while the installation process is running.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

During Pulp 2.8.3 installation, RSA keys used for server-consumer message validation could briefly be created in a world-readable location. A local user on the same host might copy them during installation. This is mainly a local, timing-dependent exposure, not evidence of remote compromise. Most relevant to organizations that installed Pulp 2.8.3 on shared or multi-user Linux systems. Single-purpose hosts with no untrusted local users have lower practical exposure, though post-install key trust should still be reviewed. Prioritize remediation where Pulp ran on shared infrastructure or systems with multiple local users. This is not presented as remotely exploitable, but exposed trust keys can undermine system assurance and should be handled as a credential exposure concern. Mitigation focus: Review Red Hat RHBA-2016:1501 and Pulp guidance for fixed packages.; Upgrade or reinstall affected Pulp packages using vendor-supported instructions.; Treat keys from exposed installations as potentially compromised..

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.

cve · low confidence lookup

CVE-2016-3111 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
6Source 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.