Ansible Semaphore up to 2.8.88 api/auth.go improper authentication
|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.
A vulnerability, which was classified as critical, has been found in Ansible Semaphore up to 2.8.88. This issue affects an unknown function of the file api/auth.go. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
api/auth.go in Ansible Semaphore before 2.8.89 mishandles authentication.
The weakness was released 03/19/2023 as 3e4a62b7f2b1ef0660c9fb839818a53c80a5a8b1. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-28609 since 03/18/2023. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.8.89 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 3e4a62b7f2b1ef0660c9fb839818a53c80a5a8b1 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.
CVSSv3VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Improper authentication
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: Semaphore 2.8.89
Timeline03/18/2023 CVE reserved
03/19/2023 +1 days Advisory disclosed
03/19/2023 +0 days VulDB entry created
04/11/2023 +23 days VulDB last update
CVE: CVE-2023-28609 (🔒)
EntryCreated: 03/19/2023 08:07 AM
Updated: 04/11/2023 10:58 PM
Changes: 03/19/2023 08:07 AM (44), 04/11/2023 10:58 PM (11)
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!
No comments yet. Languages: en.
Please log in to comment.