CVE-2013-4346: oauth2 Replay Attack Vulnerability
Summary
CVE-2013-4346: The Server.verify_request function in SimpleGeo python-oauth2 does not check the nonce, which allows remote attackers to perform replay attacks via a signed URL. Affects oauth2 versions < 1.9rc1. Fixed in 1.9rc1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The oauth2 package is a Python library that provides OAuth 1.0/a, OAuth 2.0, and Service Account credentials (JWT) for accessing Google APIs. It is commonly used for authentication and authorization purposes in Python applications. However, a vulnerability has been identified in the package that allows remote attackers to perform replay attacks via a signed URL.
Vulnerability Detail
The Server.verify_request function in SimpleGeo python-oauth2 does not check the nonce, which allows remote attackers to perform replay attacks via a signed URL. This means that an attacker can intercept a signed URL and replay it multiple times, potentially gaining unauthorized access or performing malicious actions on behalf of the original user. The lack of nonce verification makes it easier for an attacker to reuse the signed URL without detection.
How To Fix
Minimum fixed version
1.9rc1
This is the first release that contains the fix.
pip install --upgrade "oauth2==1.9rc1"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to update the oauth2 package to the fixed version.
Conclusion
The oauth2 package is vulnerable to a replay attack due to the lack of nonce verification in the Server.verify_request function. To mitigate this vulnerability, it is crucial to update the package to version 1.9rc1 or later. Failure to address this issue may result in unauthorized access or malicious actions on behalf of users. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for oauth2 →
FAQ
This vulnerability allows remote attackers to perform replay attacks, potentially gaining unauthorized access or performing malicious actions on behalf of the original user.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply input your Pipfile.lock file, and the tool will alert you if the vulnerability is present.
There are no known public exploits for this vulnerability at the moment. However, it is crucial to update the oauth2 package to mitigate the risk of potential attacks.
You can find more details about this vulnerability in the advisory database at https://github.com/pypa/advisory-database/blob/main/vulns/oauth2/PYSEC-2014-85.yaml
To update the oauth2 package, you can use the following command: pip install --upgrade oauth2
Related vulnerabilities
Recent vulnerabilities recorded for oauth2.
