Opmantek Open-AudIT 3.5.x util.php 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.
6.0$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Opmantek Open-AudIT 3.5.x. This issue affects some unknown processing of the file code_igniter/application/controllers/util.php. The manipulation leads to improper authentication. This vulnerability is referenced as CVE-2021-40612. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Opmantek Open-AudIT 3.5.x. This issue affects an unknown code of the file code_igniter/application/controllers/util.php. 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 product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability.

The weakness was published 12/22/2021. The advisory is shared at community.opmantek.com. The identification of this vulnerability is CVE-2021-40612 since 09/07/2021. Technical details are known, but no exploit is available.

By approaching the search of inurl:code_igniter/application/controllers/util.php it is possible to find vulnerable targets with Google Hacking.

Applying the patch c7595cbb092e410a487f03c0eb536cf19e538860 is able to eliminate this problem. The bugfix is ready for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

Website

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: Improper authentication
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: c7595cbb092e410a487f03c0eb536cf19e538860

Timelineinfo

09/07/2021 🔍
12/22/2021 +106 days 🔍
12/22/2021 +0 days 🔍
12/25/2021 +3 days 🔍

Sourcesinfo

Product: github.com

Advisory: c7595cbb092e410a487f03c0eb536cf19e538860
Status: Confirmed

CVE: CVE-2021-40612 (🔍)
GCVE (CVE): GCVE-0-2021-40612
GCVE (VulDB): GCVE-100-188885

Entryinfo

Created: 12/22/2021 17:39
Updated: 12/25/2021 16:44
Changes: 12/22/2021 17:39 (40), 12/25/2021 16:44 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider 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!