Kayako liveResponse 2.0 Error Message addressbook.php information disclosure

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

Summaryinfo

A vulnerability has been found in Kayako liveResponse 2.0 and classified as problematic. This affects an unknown function of the file addressbook.php of the component Error Message Handler. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2005-2463. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Kayako liveResponse 2.0. This affects an unknown part of the file addressbook.php of the component Error Message Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:

Kayako liveResponse 2.x allows remote attackers to obtain sensitive information via a direct request to addressbook.php and other include scripts, which reveals the path in an error message.

The bug was discovered 03/01/2005. The weakness was shared 07/30/2005 by James Bercegay with Gulftech (Website). The advisory is shared at gulftech.org. This vulnerability is uniquely identified as CVE-2005-2463 since 08/05/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.

After before and not just, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 151 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:addressbook.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 19335 (Kayako LiveResponse Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

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 X-Force (21685), Tenable (19335), SecurityFocus (BID 14425†), OSVDB (18399†) and Secunia (SA16286†). The entries VDB-27848, VDB-27847, VDB-27846 and VDB-82822 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 19335
Nessus Name: Kayako LiveResponse Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/01/2005 🔍
07/30/2005 +151 days 🔍
07/30/2005 +0 days 🔍
07/30/2005 +0 days 🔍
07/30/2005 +0 days 🔍
08/01/2005 +1 days 🔍
08/01/2005 +0 days 🔍
08/01/2005 +0 days 🔍
08/05/2005 +3 days 🔍
12/31/2005 +148 days 🔍
06/18/2006 +169 days 🔍
03/12/2015 +3189 days 🔍
06/20/2019 +1561 days 🔍

Sourcesinfo

Advisory: gulftech.org
Researcher: James Bercegay
Organization: Gulftech
Status: Not defined

CVE: CVE-2005-2463 (🔍)
GCVE (CVE): GCVE-0-2005-2463
GCVE (VulDB): GCVE-100-27849
X-Force: 21685
SecurityFocus: 14425 - Kayako LiveResponse Multiple Input Validation Vulnerabilities
Secunia: 16286 - Kayako LiveResponse Multiple Vulnerabilities, Moderately Critical
OSVDB: 18399 - Kayako LiveResponse Include Scripts Direct Request Path Disclosure
Vulnerability Center: 11934 - Kayako LiveResponse Discloses Information via Error Message, Medium

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

Entryinfo

Created: 03/12/2015 11:11
Updated: 06/20/2019 18:09
Changes: 03/12/2015 11:11 (66), 06/20/2019 18:09 (13)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!