CVE-2016-3111: Infoleak

Published Apr 12, 2016
·
Updated

It was found that spec file generating RSA keys, used for authenticating messages between server and consumers, as post installation step does this in world-readable directories for a brief moment.

Vulnerable code:

https://github.com/pulp/pulp/blob/master/pulp.spec#L473-L486 https://github.com/pulp/pulp/blob/master/pulp.spec#L894-L903

Other sources

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.

MITRE

Affected Software

1 affected component
Pulpproject Pulp<=2.8.2-1

Event History

Apr 12, 2016
Data Sourced
09:07 AM
DescriptionSeverityAffected Software
Jun 8, 2017
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-3111?

CVE-2016-3111 has been rated as a low-severity vulnerability due to the brief exposure of RSA keys in world-readable directories.

2

How do I fix CVE-2016-3111?

To fix CVE-2016-3111, ensure the generation of RSA keys occurs in a secure, non-world-readable directory during the post-installation process.

3

What software versions are affected by CVE-2016-3111?

CVE-2016-3111 affects all versions of the Pulp Project up to and including 2.8.2-1.

4

What type of vulnerability is CVE-2016-3111?

CVE-2016-3111 is classified as an exposure of sensitive information vulnerability.

5

Is CVE-2016-3111 exploitable remotely?

CVE-2016-3111 is not directly exploitable remotely, but it poses a risk if an attacker gains access to the server during the key generation phase.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203