FreeBSD up to 5.4 /dev/iir Remote Code Execution

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

Summaryinfo

A vulnerability was found in FreeBSD up to 5.4. It has been classified as problematic. This impacts an unknown function of the file /dev/iir. Performing a manipulation results in Remote Code Execution. This vulnerability is identified as CVE-2005-1399. The attack can only be performed from the local network. Additionally, an exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability, which was classified as problematic, was found in FreeBSD up to 5.4 (Operating System). This affects an unknown code block of the file /dev/iir. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

FreeBSD 4.6 to 4.11 and 5.x to 5.4 uses insecure default permissions for the /dev/iir device, which allows local users to execute restricted ioctl calls to read or modify data on hardware that is controlled by the iir driver.

The bug was discovered 05/06/2005. The weakness was released 05/06/2005 by Christian S.J. Peron (Website). The advisory is shared at ftp.freebsd.org. This vulnerability is uniquely identified as CVE-2005-1399 since 05/03/2005. Access to the local network is required for this attack. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 52665 (Fedora 14 : pidgin-2.7.11-1.fc14 (2011-3113)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l.

Upgrading to version 5.x eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at ftp.FreeBSD.org. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published 7 years after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (20426), Tenable (52665), SecurityFocus (BID 13525†), OSVDB (16090†) and Secunia (SA15260†). Entries connected to this vulnerability are available at VDB-1463 and VDB-1462. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 5.7

VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Access: Public
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 52665
Nessus Name: Fedora 14 : pidgin-2.7.11-1.fc14 (2011-3113)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 52665
OpenVAS Name: FreeBSD Security Advisory (FreeBSD-SA-05:06.iir.asc)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

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

Upgrade: FreeBSD 5.x
Patch: ftp.FreeBSD.org

Timelineinfo

05/03/2005 🔍
05/06/2005 +3 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/06/2005 +0 days 🔍
05/30/2005 +23 days 🔍
06/04/2006 +370 days 🔍
03/11/2011 +1741 days 🔍
03/15/2011 +4 days 🔍
03/11/2021 +3649 days 🔍

Sourcesinfo

Product: freebsd.org

Advisory: ftp.freebsd.org
Researcher: Christian S.J. Peron
Status: Confirmed

CVE: CVE-2005-1399 (🔍)
GCVE (CVE): GCVE-0-2005-1399
GCVE (VulDB): GCVE-100-1461
X-Force: 20426 - FreeBSD iir driver file permissions, High Risk
SecurityFocus: 13525 - FreeBSD IIR(4) Driver Incorrect Permissions Vulnerability
Secunia: 15260 - FreeBSD Insecure iir Driver Permissions, Less Critical
OSVDB: 16090 - FreeBSD /dev/iir Permission Weakness Privilege Escalation
SecurityTracker: 1013904
Vulnerability Center: 11750 - FreeBSD /dev/iir Device Insecure Default Permissions Allow Local Execution of Restricted ioctl Calls, Medium

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

Entryinfo

Created: 05/30/2005 11:14
Updated: 03/11/2021 11:25
Changes: 05/30/2005 11:14 (96), 07/02/2019 20:43 (2), 03/11/2021 11:25 (2)
Complete: 🔍
Cache ID: 216:BDC: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 want to use VulDB in your project?

Use the official API to access entries easily!