What is the severity of CVE-2016-3696?

CVE-2016-3696 has a moderate severity rating due to the potential exposure of sensitive CA keys to local users.

How do I fix CVE-2016-3696?

To fix CVE-2016-3696, upgrade Pulp to version 2.8.5 or later to ensure the creation of certificate files in a secure environment.

Who is affected by CVE-2016-3696?

CVE-2016-3696 affects Fedora 24 systems and Pulp versions up to and including 2.8.4.

What vulnerability does CVE-2016-3696 address?

CVE-2016-3696 addresses a vulnerability that allows local users to access the CA key due to insecure file permissions.

Is CVE-2016-3696 still a risk in newer versions?

No, CVE-2016-3696 is not a risk in newer versions of Pulp beyond 2.8.5, as the issue has been resolved.

Vulnerability/
CVE-2016-3696

medium

5.5

CWE

200

20/4/2016

13/6/2017

6/8/2024

CVE-2016-3696: Infoleak

First published: Wed Apr 20 2016(Updated: )

The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Fedora	=24
Pulp Project	<=2.8.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-3696?
CVE-2016-3696 has a moderate severity rating due to the potential exposure of sensitive CA keys to local users.
How do I fix CVE-2016-3696?
To fix CVE-2016-3696, upgrade Pulp to version 2.8.5 or later to ensure the creation of certificate files in a secure environment.
Who is affected by CVE-2016-3696?
CVE-2016-3696 affects Fedora 24 systems and Pulp versions up to and including 2.8.4.
What vulnerability does CVE-2016-3696 address?
CVE-2016-3696 addresses a vulnerability that allows local users to access the CA key due to insecure file permissions.
Is CVE-2016-3696 still a risk in newer versions?
No, CVE-2016-3696 is not a risk in newer versions of Pulp beyond 2.8.5, as the issue has been resolved.

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

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-3696?
CVE-2016-3696 has a moderate severity rating due to the potential exposure of sensitive CA keys to local users.
How do I fix CVE-2016-3696?
To fix CVE-2016-3696, upgrade Pulp to version 2.8.5 or later to ensure the creation of certificate files in a secure environment.
Who is affected by CVE-2016-3696?
CVE-2016-3696 affects Fedora 24 systems and Pulp versions up to and including 2.8.4.
What vulnerability does CVE-2016-3696 address?
CVE-2016-3696 addresses a vulnerability that allows local users to access the CA key due to insecure file permissions.
Is CVE-2016-3696 still a risk in newer versions?
No, CVE-2016-3696 is not a risk in newer versions of Pulp beyond 2.8.5, as the issue has been resolved.