Linux-ha heartbeat 2.0.5 Shared Memory heartbeat.c access control

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Linux-ha heartbeat 2.0.5. Impacted is an unknown function of the file heartbeat.c of the component Shared Memory. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2006-3815. Moreover, an exploit is present. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux-ha heartbeat 2.0.5 and classified as problematic. This issue affects an unknown functionality of the file heartbeat.c of the component Shared Memory. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is availability. The summary by CVE is:

heartbeat.c in heartbeat before 2.0.6 sets insecure permissions in a shmget call for shared memory, which allows local users to cause an unspecified denial of service via unknown vectors, possibly during a short time window on startup.

The bug was discovered 07/22/2006. The weakness was disclosed 07/25/2006 (Website). It is possible to read the advisory at mail-archive.com. The identification of this vulnerability is CVE-2006-3815 since 07/24/2006. The exploitation is known to be easy. Attacking locally is a requirement. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

A public exploit has been developed in ANSI C. The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 22670 (Debian DSA-1128-1 : heartbeat - permission error), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l.

Upgrading to version 2.0.6 eliminates this vulnerability. A possible mitigation has been published 3 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (28035), Exploit-DB (28287), Tenable (22670), SecurityFocus (BID 19186†) and OSVDB (27555†). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 3.6

VulDB Base Score: 4.0
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22670
Nessus Name: Debian DSA-1128-1 : heartbeat - permission error
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 57165
OpenVAS Name: Debian Security Advisory DSA 1128-1 (heartbeat)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: heartbeat 2.0.6

Timelineinfo

07/22/2006 🔍
07/24/2006 +2 days 🔍
07/25/2006 +1 days 🔍
07/25/2006 +0 days 🔍
07/25/2006 +0 days 🔍
07/27/2006 +2 days 🔍
07/27/2006 +0 days 🔍
07/28/2006 +1 days 🔍
07/28/2006 +0 days 🔍
09/04/2006 +38 days 🔍
10/14/2006 +40 days 🔍
03/12/2015 +3071 days 🔍
02/02/2025 +3615 days 🔍

Sourcesinfo

Advisory: mail-archive.com
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2006-3815 (🔍)
GCVE (CVE): GCVE-0-2006-3815
GCVE (VulDB): GCVE-100-31487
X-Force: 28035
SecurityFocus: 19186 - Linux-HA Heartbeat Insecure Default Permissions on Shared Memory Vulnerability
Secunia: 21162 - Heartbeat Shared Memory Insecure Permissions Denial of Service, Not Critical
OSVDB: 27555 - Linux-HA - Heartbeat - Insecure Default Permissions on Shared Memory Issue
SecurityTracker: 1016602
Vulnerability Center: 12624 - Linux HA Heartbeat Denial of Service due to Shared Memory Insecure Permissions, Medium
Vupen: ADV-2006-2994

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 03/12/2015 14:25
Updated: 02/02/2025 13:11
Changes: 03/12/2015 14:25 (88), 06/24/2019 18:08 (5), 02/02/2025 13:11 (17)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!