Nama: Exposed IOCTL with Insufficient Access Control

The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

Informasi Umum

Mode Pengenalan

Architecture and Design
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Platform yang Berlaku

Bahasa

Nama: C (Often)
Nama: C++ (Often)

Sistem Operasi

Kelas: Unix (Undetermined)
Kelas: Windows (Undetermined)

Konsekuensi Umum

Cakupan	Dampak	Kemungkinan
Integrity Availability Confidentiality	Varies by Context Catatan: Attackers can invoke any functionality that the IOCTL offers. Depending on the functionality, the consequences may include code execution, denial-of-service, and theft of data.

Contoh yang Diamati

Referensi	Deskripsi
CVE-2009-2208	Operating system does not enforce permissions on an IOCTL that can be used to modify network settings.
CVE-2008-3831	Device driver does not restrict ioctl calls to its direct rendering manager.
CVE-2008-3525	ioctl does not check for a required capability before processing certain requests.
CVE-2008-0322	Chain: insecure device permissions allows access to an IOCTL, allowing arbitrary memory to be overwritten.
CVE-2007-4277	Chain: anti-virus product uses weak permissions for a device, leading to resultant buffer overflow in an exposed IOCTL.
CVE-2007-1400	Chain: sandbox allows opening of a TTY device, enabling shell commands through an exposed ioctl.
CVE-2006-4926	Anti-virus product uses insecure security descriptor for a device driver, allowing access to a privileged IOCTL.
CVE-1999-0728	Unauthorized user can disable keyboard or mouse by directly invoking a privileged IOCTL.

Mitigasi yang Memungkinkan

Phases : Architecture and Design
In Windows environments, use proper access control for the associated device or device namespace. See References.

Catatan Pemetaan Kerentanan

Justifikasi : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentar : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Catatan

This can be primary to many other weaknesses when the programmer assumes that the IOCTL can only be accessed by trusted parties. For example, a program or driver might not validate incoming addresses in METHOD_NEITHER IOCTLs in Windows environments (CWE-781), which could allow buffer overflow and similar attacks to take place, even when the attacker never should have been able to access the IOCTL at all.

Referensi

REF-701

Securing Device Objects
Microsoft.
https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/controlling-device-access

Pengajuan

Nama	Organisasi	Tanggal	Tanggal rilis	Version
CWE Content Team	MITRE	2009-07-15 +00:00	2009-07-27 +00:00	1.5

Modifikasi

Nama	Organisasi	Tanggal	Komentar
CWE Content Team	MITRE	2009-12-28 +00:00	updated Time_of_Introduction
CWE Content Team	MITRE	2017-11-08 +00:00	updated Likelihood_of_Exploit, Modes_of_Introduction, Relationships
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2021-03-15 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated References, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2023-10-26 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2025-12-11 +00:00	updated Weakness_Ordinalities

Detail CWE-782

CWE-782