Lasso up to 2.6.x signature verification

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

Summaryinfo

A vulnerability was found in Lasso up to 2.6.x and classified as problematic. Affected is an unknown function. Executing a manipulation can lead to signature verification. This vulnerability is tracked as CVE-2021-28091. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Lasso up to 2.6.x. It has been declared as problematic. This vulnerability affects an unknown code. The manipulation with an unknown input leads to a signature verification vulnerability. The CWE definition for the vulnerability is CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. As an impact it is known to affect integrity.

The weakness was disclosed 06/04/2021. The advisory is available at debian.org. This vulnerability was named CVE-2021-28091. The technical details are unknown and an exploit is not available.

The vulnerability scanner Nessus provides a plugin with the ID 239883 (TencentOS Server 3: lasso (TSSA-2022:0247)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 2.7.0 eliminates this vulnerability. The upgrade is hosted for download at git.entrouvert.org. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.entrouvert.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (239883). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.5

VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Signature verification
CWE: CWE-347 / CWE-345
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

Nessus ID: 239883
Nessus Name: TencentOS Server 3: lasso (TSSA-2022:0247)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Lasso 2.7.0
Patch: git.entrouvert.org

Timelineinfo

03/08/2021 🔍
06/04/2021 +87 days 🔍
06/04/2021 +0 days 🔍
06/19/2025 +1475 days 🔍

Sourcesinfo

Advisory: debian.org
Status: Confirmed

CVE: CVE-2021-28091 (🔍)
GCVE (CVE): GCVE-0-2021-28091
GCVE (VulDB): GCVE-100-176362

Entryinfo

Created: 06/04/2021 21:32
Updated: 06/19/2025 00:08
Changes: 06/04/2021 21:32 (37), 06/10/2021 07:07 (5), 06/19/2025 00:08 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!