dbcve.org
Stripe ApiApplication · Stripe

CVE-2018-19249

HIGH · 7.5 CVSS v3.0 Published 2019-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Stripe API v1 allows remote attackers to bypass intended access restrictions by replaying api.stripe.com /v1/tokens XMLHttpRequest data, parsing the response under the object card{}, and reading the cvc_check information if the creation is successful without charging the actual card used in the transaction.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Stripe API v1 reportedly allows remote attackers to bypass intended access restrictions by replaying api.stripe.com /v1/tokens XMLHttpRequest data. The attack involves parsing the response under the card{} object to read cvc_check information when token creation succeeds without charging the card.

MitigationImplement request replay protection (unique nonces/tokens), enforce proper authentication on all token creation endpoints, and validate that CVC check results are only returned to authorized parties.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Stripe ApiApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Stripe API version in use
    Review your codebase for API calls to stripe.com and check which API version is specified in your Stripe client configuration or requests (e.g., Stripe API v1, v2, v3). Look for version headers or initialization parameters.
    Affected if Your integration explicitly uses Stripe API v1 (version 1.0) or the Stripe library defaults to v1 without explicit version specification.
  2. Verify token creation endpoint usage
    Audit your application code that interacts with Stripe's /v1/tokens endpoint. Identify where token creation requests are made and how they are handled.
    Affected if Your application creates payment tokens via Stripe's API without additional server-side validation or uses client-side token creation that exposes token data.
  3. Check for replay protection mechanisms
    Review your implementation to determine whether each token creation request includes unique identifiers, nonces, orCSRF tokens that prevent reuse of the same request.
    Affected if Your token creation requests can be replayed with identical parameters and produce the same valid response, indicating no unique nonce or replay protection is implemented.
  4. Inspect token response handling
    Examine how your application processes responses from Stripe token creation, specifically whether cvc_check results from the card{} object are exposed to unauthorized users or client-side code.
    Affected if Your application returns or exposes cvc_check information from Stripe token responses to parties that should not have access to verification results.
  5. Review API key permissions and scope
    Check the permissions assigned to your Stripe API keys using the Stripe dashboard. Determine whether keys used for token creation have overly broad access.
    Affected if Your Stripe API keys have more permissions than necessary and could allow an attacker with compromised keys to exploit the replay vulnerability.

You are affected if your integration relies on Stripe API v1 without replay protection and exposes token response data including cvc_check results to unauthorized parties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement request replay protection (unique nonces/tokens), enforce proper authentication on all token creation endpoints, and validate that CVC check results are only returned to authorized parties.

Fix this in Stripe Api Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-19249 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-19249 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data