snipe-it up to 6.4.1 API authorization

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability was found in snipe-it up to 6.4.1. It has been classified as problematic. Affected by this issue is some unknown functionality of the component API. Performing a manipulation results in authorization. This vulnerability is known as CVE-2024-5685. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in snipe-it up to 6.4.1. It has been classified as problematic. This affects an unknown code block of the component API. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity. The summary by CVE is:

Users with "User:edit" and "Self:api" permissions can promote or demote themselves or other users by performing changes to the group's memberships via API call.This issue affects snipe-it: from v4.6.17 through v6.4.1.

The weakness was published by Davide Ferreira. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-5685 since 06/06/2024. Neither technical details nor an exploit are publicly available.

Upgrading to version 6.4.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 34f1ea1c0ecd403047cd1327569ee391a7201cc1 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.6
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: snipe-it 6.4.2
Patch: 34f1ea1c0ecd403047cd1327569ee391a7201cc1

Timelineinfo

06/06/2024 🔍
06/14/2024 +8 days 🔍
06/14/2024 +0 days 🔍
06/18/2024 +4 days 🔍

Sourcesinfo

Advisory: github.com
Researcher: Davide Ferreira
Status: Confirmed

CVE: CVE-2024-5685 (🔍)
GCVE (CVE): GCVE-0-2024-5685
GCVE (VulDB): GCVE-100-268665

Entryinfo

Created: 06/14/2024 12:47
Updated: 06/18/2024 15:04
Changes: 06/14/2024 12:47 (56), 06/15/2024 11:00 (1), 06/18/2024 15:04 (11)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!