| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in F21 JWT up to 1.x. Affected by this issue is some unknown functionality of the file JWT.php of the component Signature Handler. The manipulation results in input validation. This vulnerability is cataloged as CVE-2015-2951. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability was found in F21 JWT up to 1.x. It has been classified as critical. Affected is some unknown functionality of the file JWT.php of the component Signature Handler. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
JWT.php in F21 JWT before 2.0 allows remote attackers to bypass signature verification via crafted tokens.
The weakness was shared 06/05/2015 by Toshiharu Sugiyama (Website). The advisory is available at github.com. This vulnerability is traded as CVE-2015-2951 since 04/07/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit.
By approaching the search of inurl:JWT.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 75021†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/F21/jwt/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JWT 2.0
Patch: github.com
Timeline
04/07/2015 🔍06/03/2015 🔍
06/05/2015 🔍
06/05/2015 🔍
06/07/2015 🔍
05/20/2022 🔍
Sources
Product: github.comAdvisory: a327cf9052df8f9f97728ca0b5fa78a8231b79b6
Researcher: Toshiharu Sugiyama
Status: Not defined
Confirmation: 🔍
CVE: CVE-2015-2951 (🔍)
GCVE (CVE): GCVE-0-2015-2951
GCVE (VulDB): GCVE-100-75714
SecurityFocus: 75021 - F21 JWT CVE-2015-2951 Security Bypass Vulnerability
Entry
Created: 06/07/2015 17:54Updated: 05/20/2022 08:37
Changes: 06/07/2015 17:54 (51), 04/04/2019 06:36 (4), 05/20/2022 08:37 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.