biscuit-auth biscuit-rust prior 5.0.0 privileges management
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in biscuit-auth biscuit-rust. Affected by this vulnerability is an unknown functionality. The manipulation leads to privileges management. This vulnerability is known as CVE-2024-41949. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability classified as problematic has been found in biscuit-auth biscuit-rust. Affected is an unknown function. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
biscuit-rust is the Rust implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a ThirdPartyBlock request can be sent, providing only the necessary info to generate a third-party block and to sign it, which includes the public key of the previous block (used in the signature) and the public keys part of the token symbol table (for public key interning in datalog expressions). A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-41949 since 07/24/2024. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation requires an enhanced level of successful authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 5.0.0 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.4
NVD Vector: 🔒
CNA Base Score: 3.0
CNA Vector (GitHub_M): 🔒
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
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: biscuit-rust 5.0.0
Timeline
07/24/2024 CVE reserved08/02/2024 Advisory disclosed
08/02/2024 VulDB entry created
08/09/2024 VulDB entry last update
Sources
Advisory: GHSA-p9w4-585h-g3c7Status: Confirmed
CVE: CVE-2024-41949 (🔒)
GCVE (CVE): GCVE-0-2024-41949
GCVE (VulDB): GCVE-100-273420
Entry
Created: 08/02/2024 07:12 AMUpdated: 08/09/2024 09:16 PM
Changes: 08/02/2024 07:12 AM (63), 08/09/2024 09:16 PM (13)
Complete: 🔍
Cache ID: 18:529:40
No comments yet. Languages: en.
Please log in to comment.