CVE-2017-1002151
First published: Thu Sep 14 2017(Updated: )
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
Credit: patrick@puiterwijk.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Pagure | <=3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-1002151?
CVE-2017-1002151 is considered a medium severity vulnerability due to its potential for loss of confidentiality.
How do I fix CVE-2017-1002151?
To fix CVE-2017-1002151, update Red Hat Pagure to version 3.3.1 or later.
What specific versions of Pagure are affected by CVE-2017-1002151?
Pagure versions 3.3.0 and earlier are affected by CVE-2017-1002151.
What type of vulnerability is CVE-2017-1002151?
CVE-2017-1002151 is an authorization vulnerability that can lead to loss of confidentiality.
Is CVE-2017-1002151 a common vulnerability?
CVE-2017-1002151 has been identified in earlier versions of Pagure, making it a notable vulnerability for users of that software.
- agent/type
- agent/weakness
- agent/references
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/remedy
- agent/last-modified-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/redhat
- canonical/red hat pagure
- version/red hat pagure/3.3