lynx up to 2.8.6 URL privileges management

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

Summaryinfo

A vulnerability, which was classified as critical, has been found in lynx up to 2.8.6. Affected by this issue is some unknown functionality of the component URL Handler. Performing a manipulation results in privileges management. This vulnerability is identified as CVE-2008-4690. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as very critical, was found in lynx up to 2.8.6 (Web Browser). This affects an unknown functionality of the component URL Handler. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

lynx 2.8.6dev.15 and earlier, when advanced mode is enabled and lynx is configured as a URL handler, allows remote attackers to execute arbitrary commands via a crafted lynxcgi: URL, a related issue to CVE-2005-2929. NOTE: this might only be a vulnerability in limited deployments that have defined a lynxcgi: handler.

The bug was discovered 10/09/2008. The weakness was released 10/22/2008 (Website). The advisory is shared at redhat.com. This vulnerability is uniquely identified as CVE-2008-4690 since 10/22/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/20/2019). MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 13 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 40062 (openSUSE Security Update : lynx (lynx-275)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165646 (SUSE Enterprise Linux Security Update (SUSE-SR:2009:002)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (46248), Tenable (40062), OSVDB (49479†), Secunia (SA32416†) and SecurityTracker (ID 1021105†). Entries connected to this vulnerability are available at VDB-36551, VDB-39487, VDB-45741 and VDB-45645. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / 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

Nessus ID: 40062
Nessus Name: openSUSE Security Update : lynx (lynx-275)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 880143
OpenVAS Name: Centreon command_name Parameter Remote Command Execution Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

10/09/2008 🔍
10/09/2008 +0 days 🔍
10/22/2008 +13 days 🔍
10/22/2008 +0 days 🔍
10/22/2008 +0 days 🔍
10/27/2008 +5 days 🔍
10/30/2008 +3 days 🔍
11/02/2008 +3 days 🔍
07/21/2009 +261 days 🔍
03/17/2015 +2065 days 🔍
08/20/2019 +1617 days 🔍

Sourcesinfo

Advisory: redhat.com
Status: Not defined

CVE: CVE-2008-4690 (🔍)
GCVE (CVE): GCVE-0-2008-4690
GCVE (VulDB): GCVE-100-44661

OVAL: 🔍

X-Force: 46248
Secunia: 32416
OSVDB: 49479 - CVE-2008-4690 - Lynx - Command Execution Issue
SecurityTracker: 1021105
Vulnerability Center: 19904 - Lynx <= 2.8.6dev.15 Remote User-Assisted Code Execution via a Crafted lynxcgi: URL, Medium

See also: 🔍

Entryinfo

Created: 03/17/2015 16:11
Updated: 08/20/2019 09:43
Changes: 03/17/2015 16:11 (71), 08/20/2019 09:43 (10)
Complete: 🔍
Cache ID: 216:693: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 know our Splunk app?

Download it now for free!