Glewlwyd up to 2.6.0 access control

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.
6.0$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Glewlwyd up to 2.6.0. This issue affects some unknown processing. This manipulation causes access control. This vulnerability is tracked as CVE-2021-45379. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Glewlwyd up to 2.6.0. It has been declared as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was disclosed 12/30/2021 as 125281f1c0d4b6a8b49f7e55a757205a2ef01fbe. The advisory is shared at github.com. This vulnerability is known as CVE-2021-45379 since 12/20/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 2.6.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 125281f1c0d4b6a8b49f7e55a757205a2ef01fbe 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: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Access control
CWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

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: Glewlwyd 2.6.1
Patch: 125281f1c0d4b6a8b49f7e55a757205a2ef01fbe

Timelineinfo

12/20/2021 🔍
12/30/2021 +10 days 🔍
12/30/2021 +0 days 🔍
01/05/2022 +6 days 🔍

Sourcesinfo

Advisory: 125281f1c0d4b6a8b49f7e55a757205a2ef01fbe
Status: Confirmed

CVE: CVE-2021-45379 (🔍)
GCVE (CVE): GCVE-0-2021-45379
GCVE (VulDB): GCVE-100-189457

Entryinfo

Created: 12/30/2021 20:17
Updated: 01/05/2022 07:33
Changes: 12/30/2021 20:17 (41), 01/05/2022 07:33 (1)
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!