Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1457997 - (CVE-2017-7512) CVE-2017-7512 3scale AMP: validation bypass in oauth
CVE-2017-7512 3scale AMP: validation bypass in oauth
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170706,repor...
: Security
Depends On:
Blocks: 1457362
  Show dependency treegraph
 
Reported: 2017-06-01 13:30 EDT by Chess Hazlett
Modified: 2017-07-06 14:42 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It was found that RH-3scale AMP would permit creation of an access token without a client secret. An attacker could use this flaw to circumvent authentication controls and gain access to restricted APIs.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-06 14:42:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1712 normal SHIPPED_LIVE Important: Red Hat 3scale API Management Platform 2.0.0 security update 2017-07-06 17:25:45 EDT

  None (edit)
Description Chess Hazlett 2017-06-01 13:30:47 EDT
It was found that RH-3scale would permit creation of an access token without a client secret. An attacker could use this flaw to circumvent authentication controls and gain access to restricted APIs.
Comment 3 Chess Hazlett 2017-06-30 12:46:49 EDT
Acknowledgments:

Name: Ryan Nauman (TruCode)
Comment 4 errata-xmlrpc 2017-07-06 13:15:56 EDT
This issue has been addressed in the following products:

  3scale AMP 2.0

Via RHSA-2017:1712 https://access.redhat.com/errata/RHSA-2017:1712

Note You need to log in before you can comment on or make changes to this bug.