What is the severity of CVE-2016-3112?

CVE-2016-3112 has a high severity rating due to the exposure of sensitive private keys.

How do I fix CVE-2016-3112?

To fix CVE-2016-3112, upgrade to Pulp version 2.8.3 or later to ensure proper permissions on consumer private keys.

What type of vulnerability is CVE-2016-3112?

CVE-2016-3112 is a privilege escalation vulnerability caused by improper file permissions.

Who is affected by CVE-2016-3112?

Users running Pulp versions prior to 2.8.3 with improperly secured consumer private keys are affected by CVE-2016-3112.

What can attackers do with CVE-2016-3112?

Attackers can exploit CVE-2016-3112 to read consumer private keys, potentially leading to privilege escalation.

Vulnerability/
CVE-2016-3112

high

7.5

CWE

284

12/4/2016

8/6/2017

5/8/2024

CVE-2016-3112

First published: Tue Apr 12 2016(Updated: )

client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to obtain the consumer private keys and escalate privileges by reading /etc/pki/pulp/consumer/consumer-cert, and authenticating as a consumer user.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Pulp Project	<=2.8.2-1

Remedy

https://pulp.plan.io/issues/1834

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-3112?
CVE-2016-3112 has a high severity rating due to the exposure of sensitive private keys.
How do I fix CVE-2016-3112?
To fix CVE-2016-3112, upgrade to Pulp version 2.8.3 or later to ensure proper permissions on consumer private keys.
What type of vulnerability is CVE-2016-3112?
CVE-2016-3112 is a privilege escalation vulnerability caused by improper file permissions.
Who is affected by CVE-2016-3112?
Users running Pulp versions prior to 2.8.3 with improperly secured consumer private keys are affected by CVE-2016-3112.
What can attackers do with CVE-2016-3112?
Attackers can exploit CVE-2016-3112 to read consumer private keys, potentially leading to privilege escalation.

agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/remedy
agent/severity
agent/last-modified-date
agent/author
agent/references
agent/weakness
agent/description
agent/event
collector/redhat-bugzilla
source/Red Hat
alias/CVE-2016-3112
agent/trending
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/pulpproject
canonical/pulp project
version/pulp project/2.8.2-1

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2016-3112?
CVE-2016-3112 has a high severity rating due to the exposure of sensitive private keys.
How do I fix CVE-2016-3112?
To fix CVE-2016-3112, upgrade to Pulp version 2.8.3 or later to ensure proper permissions on consumer private keys.
What type of vulnerability is CVE-2016-3112?
CVE-2016-3112 is a privilege escalation vulnerability caused by improper file permissions.
Who is affected by CVE-2016-3112?
Users running Pulp versions prior to 2.8.3 with improperly secured consumer private keys are affected by CVE-2016-3112.
What can attackers do with CVE-2016-3112?
Attackers can exploit CVE-2016-3112 to read consumer private keys, potentially leading to privilege escalation.