Sun Java System Directory Server up to 6.2 Proxy Server race condition

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Sun Java System Directory Server up to 6.2. Affected is an unknown function of the component Proxy Server. This manipulation causes race condition. This vulnerability is registered as CVE-2009-4440. No exploit is available.

Detailsinfo

A vulnerability was found in Sun Java System Directory Server up to 6.2 (Directory Service Software). It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Proxy Server. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Directory Proxy Server (DPS) in Sun Java System Directory Server Enterprise Edition 6.0 through 6.3.1 does not properly handle multiple client connections within a short time window, which allows remote attackers to hijack the backend connection of an authenticated user, and obtain the privileges of this user, by making a client connection in opportunistic circumstances, related to "long binds," aka Bug Ids 6828462 and 6823593.

The weakness was published 12/28/2009 (Website). The advisory is shared at sunsolve.sun.com. This vulnerability is known as CVE-2009-4440 since 12/28/2009. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 43615 (Sun Java System Directory Proxy Server 6.x < 6.3.1.1 Multiple Vulnerabilities.), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Misc..

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (43615), SecurityFocus (BID 37481†), Secunia (SA37915†), SecurityTracker (ID 1023389†) and Vulnerability Center (SBV-24505†). Similar entries are available at VDB-51328, VDB-51327 and VDB-51326. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Support

  • end of life (old version)

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 43615
Nessus Name: Sun Java System Directory Proxy Server 6.x < 6.3.1.1 Multiple Vulnerabilities.
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 902011
OpenVAS Name: Sun Java System DSEE Multiple Vulnerabilities (Win)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/28/2009 🔍
12/28/2009 +0 days 🔍
12/28/2009 +0 days 🔍
12/28/2009 +0 days 🔍
12/28/2009 +0 days 🔍
12/28/2009 +0 days 🔍
12/28/2009 +0 days 🔍
12/30/2009 +2 days 🔍
01/04/2010 +5 days 🔍
03/18/2015 +1899 days 🔍
08/30/2021 +2357 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: sunsolve.sun.com⛔
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2009-4440 (🔍)
GCVE (CVE): GCVE-0-2009-4440
GCVE (VulDB): GCVE-100-51325

IAVM: 🔍

SecurityFocus: 37481 - Sun Java System Directory Server Multiple Remote Vulnerabilities
Secunia: 37915 - Sun Java System Directory Server Multiple Vulnerabilities, Moderately Critical
SecurityTracker: 1023389 - Sun Java System Directory Server Bugs Let Remote Users Obtain Data and Deny Service
Vulnerability Center: 24505 - Sun Java System Directory Server 6.0-6.3.1 Backend Connection Hijacking Vulnerability, Medium
Vupen: ADV-2009-3647

See also: 🔍

Entryinfo

Created: 03/18/2015 15:15
Updated: 08/30/2021 11:03
Changes: 03/18/2015 15:15 (65), 02/19/2017 09:41 (17), 08/30/2021 11:03 (3)
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!