5406 matches found
Meet JWT heartbreaker, a Burp extension that finds thousands weak secrets automatically
In the recent post https://lab.wallarm.com/340-weak-jwt-secrets-you-should-check-in-your-code/, we presented a wallarm/jwt-secrets GitHub repository with a 340 JSON Web Token secrets available publicly. Using this data, its possible to check if you or your developers forgot to change default...
Meet JWT heartbreaker, a Burp extension that finds thousands weak secrets automatically
In the recent post https://wlrm210771357.wpcomstaging.com/340-weak-jwt-secrets-you-should-check-in-your-code/, we presented a wallarm/jwt-secrets GitHub repository with a 340 JSON Web Token secrets available publicly. Using this data, its possible to check if you or your developers forgot to chan...
DLA-2390-1 ruby-json-jwt - security update
Bulletin has no description...
CVE-2020-26160
A vulnerability was found in jwt-go where it is vulnerable to Access Restriction Bypass if m"aud" happens to be string, as allowed by the spec, the type assertion fails and the value of aud is "". This can cause audience verification to succeed even if the audiences being passed are incorrect if...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
Design/Logic Flaw
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
The CVE-2020-26160 entry concerns jwt-go prior to 4.0.0-preview1. The vulnerability allows bypass of audience restrictions when m["aud"] is []string{}; due to a type assertion failure, aud becomes the empty string, which is problematic if a service does not enforce its own audience checks. The pr...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
CVE-2020-26160
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
Authorization Bypass
github.com/dgrijalva/jwt-go is vulnerable to authorization bypass. The vulnerability exists as the audience verification succeeds even if the type assertion fails when the value of aud is ""...
PT-2020-16317
Name of the Vulnerable Software and Affected Versions jwt-go versions prior to 4.0.0-preview1 jwt-go before 4.0.0-preview1 Description The issue allows attackers to bypass intended access restrictions in situations where the audience claim in a JWT token is an array of strings, rather than a sing...
CVE-2020-26160: Improper Authentication
jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with string for m"aud" which is allowed by the specification. Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lac...
PT-2020-14289
Name of the Vulnerable Software and Affected Versions ORY Fosite versions prior to 0.31.0 Description The uniqueness of the jti value is not checked when using "private key jwt" authentication. According to the OpenId specification, the jti assertion must be unique to prevent token reuse. However...
Security Bulletin: vulnerabilities in Nimbus JOSE+JWT affect IBM Watson Machine Learning Accelerator 1.2.1
Summary Vulnerabilities existing in the Nimbus JOSE+JWT version used by IBM Watson Machine Learning Accelerator 1.2.1. An interim fix that provides instructions on upgrading the Nimbus JOSE+JWT package to version 7.9 which resolves these vulnerabilities, are available on IBM Fix Central...
GHSA-V66P-W7QX-WV98 Authentication Bypass in express-laravel-passport
All versions of express-laravel-passport are vulnerable to an Authentication Bypass. The package fails to properly validate JWTs, allowing attackers to send HTTP requests impersonating other users. Recommendation Upgrade to version 2.0.5 or later...
PT-2020-21506
Name of the Vulnerable Software and Affected Versions express-laravel-passport versions prior to 2.0.5 Description The issue allows attackers to bypass authentication by impersonating other users due to the package's failure to properly validate JWTs. This can be achieved by sending HTTP requests...