CVE-2017-7517: Input Validation
First published: Thu Jul 13 2017(Updated: )
A user can create a project named "myProject", use that project for a while and then delete it. After the original project is deleted, another user can create a project called "myProject". Since the subjectaccessreview will now pass for this second user, they will be able to access metrics from the original project.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat OpenShift | =3.0 |
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-7517?
CVE-2017-7517 has been assigned a medium severity rating due to its potential for unauthorized access to metrics by different users.
How do I fix CVE-2017-7517?
To fix CVE-2017-7517, ensure that access controls are properly configured to prevent unauthorized users from accessing metrics after a project is deleted.
Which software is affected by CVE-2017-7517?
CVE-2017-7517 affects Red Hat OpenShift 3.0.
What type of vulnerability is CVE-2017-7517?
CVE-2017-7517 is an access control vulnerability that allows unauthorized access to resources after a project has been deleted.
Can multiple users access the same project name due to CVE-2017-7517?
Yes, CVE-2017-7517 allows different users to create projects with the same name after the original project has been deleted, leading to potential access issues.
- collector/redhat-bugzilla
- alias/CVE-2017-7517
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/references
- agent/description
- agent/event
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/redhat
- canonical/red hat openshift
- version/red hat openshift/3.0