What is the severity of CVE-2016-3108?

CVE-2016-3108 is considered a medium severity vulnerability due to its potential for local file manipulation and key leakage.

What are the consequences of CVE-2016-3108?

The consequences of CVE-2016-3108 include the risk of local attackers being able to leak sensitive keys or overwrite files due to insecure temporary file handling.

How do I fix CVE-2016-3108?

To fix CVE-2016-3108, upgrade to Pulp version 2.8.3 or later, which addresses the vulnerability.

Which versions of Pulp are affected by CVE-2016-3108?

CVE-2016-3108 affects Pulp versions up to and including 2.8.2-1.

Is CVE-2016-3108 exploited remotely?

No, CVE-2016-3108 requires local access to exploit, as it involves the local manipulation of files.

Vulnerability/
CVE-2016-3108

high

7.1

CWE

11/4/2016

8/6/2017

5/8/2024

CVE-2016-3108

First published: Mon Apr 11 2016(Updated: )

It was reported that pulp-gen-nodes-certificate script uses insecurely created temporary files for storing the generated node certificates, allowing local attackers to leak the keys or overwrite arbitrary file via symlink.

Credit: secalert@redhat.com

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

Remedy

https://github.com/pulp/pulp/pull/2528

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-3108?
CVE-2016-3108 is considered a medium severity vulnerability due to its potential for local file manipulation and key leakage.
What are the consequences of CVE-2016-3108?
The consequences of CVE-2016-3108 include the risk of local attackers being able to leak sensitive keys or overwrite files due to insecure temporary file handling.
How do I fix CVE-2016-3108?
To fix CVE-2016-3108, upgrade to Pulp version 2.8.3 or later, which addresses the vulnerability.
Which versions of Pulp are affected by CVE-2016-3108?
CVE-2016-3108 affects Pulp versions up to and including 2.8.2-1.
Is CVE-2016-3108 exploited remotely?
No, CVE-2016-3108 requires local access to exploit, as it involves the local manipulation of files.

agent/type
agent/remedy
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
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-3108
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-3108?
CVE-2016-3108 is considered a medium severity vulnerability due to its potential for local file manipulation and key leakage.
What are the consequences of CVE-2016-3108?
The consequences of CVE-2016-3108 include the risk of local attackers being able to leak sensitive keys or overwrite files due to insecure temporary file handling.
How do I fix CVE-2016-3108?
To fix CVE-2016-3108, upgrade to Pulp version 2.8.3 or later, which addresses the vulnerability.
Which versions of Pulp are affected by CVE-2016-3108?
CVE-2016-3108 affects Pulp versions up to and including 2.8.2-1.
Is CVE-2016-3108 exploited remotely?
No, CVE-2016-3108 requires local access to exploit, as it involves the local manipulation of files.