Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2016-3111: 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…

MediumCVSS 5.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: foreman (Red Hat:satellite_capsule:6.1::el6) 0:1.11.0.49-1.el6sat; foreman-debug (Red Hat:satellite_capsule:6.1::el6) 0:1.11.0.49-1.el6sat; foreman-installer (Red Hat:satellite_capsule:6.1::el6) 1:1.11.0.9-1.el6sat.

Low priority for now. Upgrade to foreman (Red Hat:satellite_capsule:6.1::el6) 0:1.11.0.49-1.el6sat; foreman-debug (Red Hat:satellite_capsule:6.1::el6) 0:1.11.0.49-1.el6sat; foreman-installer (Red Hat:satellite_capsule:6.1::el6) 1:1.11.0.9-1.el6sat or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jun 8, 2017
Updated
Jun 16, 2026
EPSS
0.3% · 33th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2016-3111

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
pulpprojectpulp

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • pulpproject pulpup to 2.8.2-1 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:satellite_capsule:6.1::el6foremanbefore 0:1.11.0.49-1.el6sat0:1.11.0.49-1.el6sat
Red Hat:satellite_capsule:6.1::el6foreman-debugbefore 0:1.11.0.49-1.el6sat0:1.11.0.49-1.el6sat
Red Hat:satellite_capsule:6.1::el6foreman-installerbefore 1:1.11.0.9-1.el6sat1:1.11.0.9-1.el6sat
Red Hat:satellite_capsule:6.1::el6foreman-installer-katellobefore 0:3.0.0.56-1.el6sat0:3.0.0.56-1.el6sat
Red Hat:satellite_capsule:6.1::el6foreman-proxybefore 0:1.11.0.4-1.el6sat0:1.11.0.4-1.el6sat
Red Hat:satellite_capsule:6.1::el6foreman-selinuxbefore 0:1.11.0.2-1.el6sat0:1.11.0.2-1.el6sat
Red Hat:satellite_capsule:6.1::el6goferbefore 0:2.7.6-1.el6sat0:2.7.6-1.el6sat
Red Hat:satellite_capsule:6.1::el6katellobefore 0:3.0.0-10.el6sat0:3.0.0-10.el6sat
Red Hat:satellite_capsule:6.1::el6katello-agentbefore 0:2.5.0-5.el6sat0:2.5.0-5.el6sat
Red Hat:satellite_capsule:6.1::el6katello-certs-toolsbefore 0:2.4.0-1.el6sat0:2.4.0-1.el6sat
Red Hat:satellite_capsule:6.1::el6katello-client-bootstrapbefore 0:1.1.0-2.el6sat0:1.1.0-2.el6sat
Red Hat:satellite_capsule:6.1::el6katello-debugbefore 0:3.0.0-10.el6sat0:3.0.0-10.el6sat
Red Hat:satellite_capsule:6.1::el6katello-installer-basebefore 0:3.0.0.56-1.el6sat0:3.0.0.56-1.el6sat
Red Hat:satellite_capsule:6.1::el6katello-selinuxbefore 0:3.0.1.2-1.el6sat0:3.0.1.2-1.el6sat
Red Hat:satellite_capsule:6.1::el6katello-servicebefore 0:3.0.0-10.el6sat0:3.0.0-10.el6sat
Red Hat:satellite_capsule:6.1::el6libqpid-dispatchbefore 0:0.4-13.el6sat0:0.4-13.el6sat
Red Hat:satellite_capsule:6.1::el6pulpbefore 0:2.8.3.3-1.el6sat0:2.8.3.3-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-admin-clientbefore 0:2.8.3.3-1.el6sat0:2.8.3.3-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-dockerbefore 0:2.0.1.1-1.el6sat0:2.0.1.1-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-docker-admin-extensionsbefore 0:2.0.1.1-1.el6sat0:2.0.1.1-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-docker-pluginsbefore 0:2.0.1.1-1.el6sat0:2.0.1.1-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-katellobefore 0:1.0.1-1.el6sat0:1.0.1-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-nodes-childbefore 0:2.8.3.3-1.el6sat0:2.8.3.3-1.el6sat
Red Hat:satellite_capsule:6.1::el6pulp-nodes-commonbefore 0:2.8.3.3-1.el6sat0:2.8.3.3-1.el6sat

+96

Other highest-scoring records for the same primary product.

  • CVE-2024-7143Pulpcore: rbac permissions incorrectly assigned in tasks that create objects
    33Monitor
  • CVE-2015-5263pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key…
    32Monitor
  • CVE-2016-3112client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable…
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2016-3107Jun 8, 2017 · The Node certificate in Pulp before 2.8.3 contains the private key, and is stored in a world-readable file in the "/etc/pki/pulp/nodes/"…
    22Monitor
  • ← EarlierCVE-2016-3108Jun 8, 2017 · The pulp-gen-nodes-certificate script in Pulp before 2.8.3 allows local users to leak the keys or write to arbitrary files via a symlink…
    28Monitor
  • Later →CVE-2018-1090Jun 18, 2018 · In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with…
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:foreman0:1.11.0.49-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:foreman-debug0:1.11.0.49-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:foreman-installer1:1.11.0.9-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:foreman-installer-katello0:3.0.0.56-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:foreman-proxy0:1.11.0.4-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:foreman-selinux0:1.11.0.2-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:gofer0:2.7.6-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:katello0:3.0.0-10.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:katello-agent0:2.5.0-5.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:katello-certs-tools0:2.4.0-1.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:katello-client-bootstrap0:1.1.0-2.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)
red hat:katello-debug0:3.0.0-10.el6sat · Red Hat:satellite_capsule:6.1::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records