Apache InLong up to 1.8.0 JDBC Connection authorization

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 identified as problematic has been detected in Apache InLong up to 1.8.0. Affected by this vulnerability is an unknown functionality of the component JDBC Connection Handler. This manipulation causes authorization. The identification of this vulnerability is CVE-2023-43668. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Apache InLong up to 1.8.0. Affected by this vulnerability is some unknown functionality of the component JDBC Connection Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. The impact remains unknown.

The weakness was shared 10/16/2023. The advisory is shared at seclists.org. This vulnerability is known as CVE-2023-43668 since 09/21/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.9.0 eliminates this vulnerability. Applying a patch 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

Vendor

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: Authorization
CWE: CWE-639 / CWE-285 / CWE-266
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: InLong 1.9.0
Patch: github.com

Timelineinfo

09/21/2023 🔍
10/16/2023 +25 days 🔍
10/16/2023 +0 days 🔍
11/02/2023 +17 days 🔍

Sourcesinfo

Vendor: apache.org
Product: github.com

Advisory: seclists.org
Status: Confirmed

CVE: CVE-2023-43668 (🔍)
GCVE (CVE): GCVE-0-2023-43668
GCVE (VulDB): GCVE-100-242209

Entryinfo

Created: 10/16/2023 07:51
Updated: 11/02/2023 16:54
Changes: 10/16/2023 07:51 (39), 11/02/2023 16:46 (1), 11/02/2023 16:54 (11)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!