What is the severity of CVE-2018-19249?

CVE-2018-19249 has a medium severity rating due to its potential for unauthorized access and information disclosure.

How do I fix CVE-2018-19249?

To mitigate CVE-2018-19249, upgrade to a patched version of the Stripe API that addresses the access control vulnerabilities.

What specific vulnerability does CVE-2018-19249 describe?

CVE-2018-19249 describes a vulnerability that allows remote attackers to bypass access restrictions by replaying API requests.

What are the consequences of exploiting CVE-2018-19249?

Exploitation of CVE-2018-19249 can lead to unauthorized access to sensitive card information, including cvc_check details.

Which version of the Stripe API is affected by CVE-2018-19249?

CVE-2018-19249 affects Stripe API version 1.0.

Vulnerability/
CVE-2018-19249

high

7.5

CWE

287

3/1/2019

31/1/2019

CVE-2018-19249

First published: Thu Jan 03 2019(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Stripe	=1.0

Never miss a vulnerability like this again

Reference Links

https://fredmooredamian.blogspot.com/2019/01/improper-authentication-on-stripe-api-v1.html

Frequently Asked Questions

What is the severity of CVE-2018-19249?
CVE-2018-19249 has a medium severity rating due to its potential for unauthorized access and information disclosure.
How do I fix CVE-2018-19249?
To mitigate CVE-2018-19249, upgrade to a patched version of the Stripe API that addresses the access control vulnerabilities.
What specific vulnerability does CVE-2018-19249 describe?
CVE-2018-19249 describes a vulnerability that allows remote attackers to bypass access restrictions by replaying API requests.
What are the consequences of exploiting CVE-2018-19249?
Exploitation of CVE-2018-19249 can lead to unauthorized access to sensitive card information, including cvc_check details.
Which version of the Stripe API is affected by CVE-2018-19249?
CVE-2018-19249 affects Stripe API version 1.0.

agent/weakness
agent/author
agent/type
agent/tags
agent/event
agent/severity
agent/references
agent/description
agent/softwarecombine
agent/first-publish-date
agent/last-modified-date
collector/nvd-index
agent/software-canonical-lookup-request
vendor/stripe
canonical/stripe
version/stripe/1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-19249?
CVE-2018-19249 has a medium severity rating due to its potential for unauthorized access and information disclosure.
How do I fix CVE-2018-19249?
To mitigate CVE-2018-19249, upgrade to a patched version of the Stripe API that addresses the access control vulnerabilities.
What specific vulnerability does CVE-2018-19249 describe?
CVE-2018-19249 describes a vulnerability that allows remote attackers to bypass access restrictions by replaying API requests.
What are the consequences of exploiting CVE-2018-19249?
Exploitation of CVE-2018-19249 can lead to unauthorized access to sensitive card information, including cvc_check details.
Which version of the Stripe API is affected by CVE-2018-19249?
CVE-2018-19249 affects Stripe API version 1.0.