reason-jose up to 0.8.1 HS256 Signature signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in reason-jose up to 0.8.1. The affected element is an unknown function of the component HS256 Signature Handler. Such manipulation leads to signature verification. This vulnerability is documented as CVE-2023-23928. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in reason-jose up to 0.8.1. It has been rated as problematic. Affected by this issue is an unknown code block of the component HS256 Signature Handler. The manipulation with an unknown input leads to a signature verification vulnerability. Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
reason-jose is a JOSE implementation in ReasonML and OCaml.`Jose.Jws.validate` does not check HS256 signatures. This allows tampering of JWS header and payload data if the service does not perform additional checks. Such tampering could expose applications using reason-jose to authorization bypass. Applications relying on JWS claims assertion to enforce security boundaries may be vulnerable to privilege escalation. This issue has been patched in version 0.8.2.
The weakness was released 02/01/2023 as GHSA-7jj9-6qwv-wpm7. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2023-23928 since 01/19/2023. There are neither technical details nor an exploit publicly available.
Upgrading to version 0.8.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 36cd724db3cbec121757624da49072386bd869e5 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: reason-jose 0.8.2
Patch: 36cd724db3cbec121757624da49072386bd869e5
Timeline
01/19/2023 🔍02/01/2023 🔍
02/01/2023 🔍
03/01/2023 🔍
Sources
Advisory: GHSA-7jj9-6qwv-wpm7Status: Confirmed
CVE: CVE-2023-23928 (🔍)
GCVE (CVE): GCVE-0-2023-23928
GCVE (VulDB): GCVE-100-219896
Entry
Created: 02/01/2023 10:29Updated: 03/01/2023 09:02
Changes: 02/01/2023 10:29 (52), 03/01/2023 09:02 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.