Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

SimpleGeo python-oauth2 does not check the nonce allowing replay attacks

CVE-2013-4346GHSA-4433-4cxq-vv73

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI oauth2

    Affected
    <= 1.9rc1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2013-4346: 2.43% estimated exploitation activity in the next 30 days; percentile 84.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

The Server.verifyrequest function in SimpleGeo python-oauth2 does not check the nonce, which allows remote attackers to perform replay attacks via a signed URL. The vulnerability does not appear to be patched according to the following discussion.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-4433-4cxq-vv73

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-4433-4cxq-vv73

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2013-4346

Advisory: SimpleGeo python-oauth2 does not check the nonce allowing replay attacks
IDs: CVE-2013-4346, GHSA-4433-4cxq-vv73
Record: https://patchnext.com/advisories/cve-2013-4346 (revision 3, source checked 26 Oct 2026, 13:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI oauth2: affected <= 1.9rc1

## Suggested inspection (read-only)
- `python -m pip show oauth2`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on oauth2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4433-4cxq-vv73 (OSV record GHSA-4433-4cxq-vv73 lists affected ranges: PyPI oauth2 >=0 <=1.9rc1)
- Verified: https://github.com/advisories/GHSA-4433-4cxq-vv73 (GitHub-reviewed advisory GHSA-4433-4cxq-vv73 lists affected ranges: PyPI oauth2 >=0 <=1.9rc1)

Commands are suggestions: review each one before running it.

Loading voting…