CVE-2016-3111

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2022-05-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
31.0%
KEV
Not listed

Published

June 8, 2017

Last Modified

May 13, 2026

References (18)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhattfm-rubygem-smart_proxy_remote_execution_ssh_core-0:0.1.2-1.el7sat2016-07-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Frequently asked(5)

What is CVE-2016-3111?
CVE-2016-3111 is a medium vulnerability published on June 8, 2017. 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…
When was CVE-2016-3111 disclosed?
CVE-2016-3111 was first published in the National Vulnerability Database on June 8, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3111 actively exploited?
CVE-2016-3111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-3111?
CVE-2016-3111 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2016-3111?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3111, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-3111

Explore →

Is Your Infrastructure Affected by CVE-2016-3111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs