OmniAuth up to 1.x failure_endpoint.rb message_key escape output

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

Summaryinfo

A vulnerability was found in OmniAuth up to 1.x. It has been declared as critical. This affects an unknown function in the library lib/omniauth/failure_endpoint.rb. Such manipulation of the argument message_key leads to escape output. This vulnerability is documented as CVE-2020-36599. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in OmniAuth up to 1.x. Affected by this issue is some unknown processing in the library lib/omniauth/failure_endpoint.rb. The manipulation of the argument message_key with an unknown input leads to a escape output vulnerability. Using CWE to declare the problem leads to CWE-116. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. Impacted is confidentiality, integrity, and availability. CVE summarizes:

lib/omniauth/failure_endpoint.rb in OmniAuth before 2.0 does not escape the message_key value.

The weakness was released 08/19/2022 as 43a396f181ef7d0ed2ec8291c939c95e3ed3ff00. The advisory is available at github.com. This vulnerability is handled as CVE-2020-36599 since 08/18/2022. Technical details are known, but there is no available exploit.

Upgrading to version 2.0 eliminates this vulnerability. Applying the patch 43a396f181ef7d0ed2ec8291c939c95e3ed3ff00 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.

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

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Escape output
CWE: CWE-116 / CWE-74 / CWE-707
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: OmniAuth 2.0
Patch: 43a396f181ef7d0ed2ec8291c939c95e3ed3ff00

Timelineinfo

08/18/2022 🔍
08/19/2022 +1 days 🔍
08/19/2022 +0 days 🔍
06/18/2024 +669 days 🔍

Sourcesinfo

Product: github.com

Advisory: 43a396f181ef7d0ed2ec8291c939c95e3ed3ff00
Status: Confirmed

CVE: CVE-2020-36599 (🔍)
GCVE (CVE): GCVE-0-2020-36599
GCVE (VulDB): GCVE-100-206786

Entryinfo

Created: 08/19/2022 13:40
Updated: 06/18/2024 19:06
Changes: 08/19/2022 13:40 (43), 09/18/2022 13:11 (11), 06/18/2024 19:06 (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 need the next level of professionalism?

Upgrade your account now!