What is the severity of CVE-2018-15121?

CVE-2018-15121 is considered a medium severity vulnerability due to its potential for CSRF attacks during authentication.

How do I fix CVE-2018-15121?

To fix CVE-2018-15121, ensure that the affected Auth0 packages are updated to versions that validate the state parameter in OAuth 2.0 and OpenID Connect protocols.

What applications are affected by CVE-2018-15121?

CVE-2018-15121 affects the Auth0 auth0-aspnet and auth0-aspnet-owin packages.

What kind of attacks does CVE-2018-15121 expose applications to?

CVE-2018-15121 exposes applications to Cross-Site Request Forgery (CSRF) attacks during authentication and authorization.

Is authentication or authorization more affected by CVE-2018-15121?

Both authentication and authorization operations are affected by CVE-2018-15121 due to the improper validation of the state parameter.

Vulnerability/
CVE-2018-15121

high

8.8

CWE

352

29/8/2018

5/8/2024

CVE-2018-15121: CSRF

First published: Wed Aug 29 2018(Updated: )

An issue was discovered in Auth0 auth0-aspnet and auth0-aspnet-owin. Affected packages do not use or validate the state parameter of the OAuth 2.0 and OpenID Connect protocols. This leaves applications vulnerable to CSRF attacks during authentication and authorization operations.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Auth0 Aspnet
Auth0 Aspnet-owin

Never miss a vulnerability like this again

Reference Links

https://auth0.com/docs/security/bulletins/cve-2018-15121

Frequently Asked Questions

What is the severity of CVE-2018-15121?
CVE-2018-15121 is considered a medium severity vulnerability due to its potential for CSRF attacks during authentication.
How do I fix CVE-2018-15121?
To fix CVE-2018-15121, ensure that the affected Auth0 packages are updated to versions that validate the state parameter in OAuth 2.0 and OpenID Connect protocols.
What applications are affected by CVE-2018-15121?
CVE-2018-15121 affects the Auth0 auth0-aspnet and auth0-aspnet-owin packages.
What kind of attacks does CVE-2018-15121 expose applications to?
CVE-2018-15121 exposes applications to Cross-Site Request Forgery (CSRF) attacks during authentication and authorization.
Is authentication or authorization more affected by CVE-2018-15121?
Both authentication and authorization operations are affected by CVE-2018-15121 due to the improper validation of the state parameter.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/author
agent/weakness
agent/last-modified-date
agent/severity
agent/tags
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/auth0
canonical/auth0 aspnet
canonical/auth0 aspnet-owin

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-15121?
CVE-2018-15121 is considered a medium severity vulnerability due to its potential for CSRF attacks during authentication.
How do I fix CVE-2018-15121?
To fix CVE-2018-15121, ensure that the affected Auth0 packages are updated to versions that validate the state parameter in OAuth 2.0 and OpenID Connect protocols.
What applications are affected by CVE-2018-15121?
CVE-2018-15121 affects the Auth0 auth0-aspnet and auth0-aspnet-owin packages.
What kind of attacks does CVE-2018-15121 expose applications to?
CVE-2018-15121 exposes applications to Cross-Site Request Forgery (CSRF) attacks during authentication and authorization.
Is authentication or authorization more affected by CVE-2018-15121?
Both authentication and authorization operations are affected by CVE-2018-15121 due to the improper validation of the state parameter.