CVE-2002-1667: Low severity FreeBSD FreeBSD vulnerability

Published Dec 31, 2002

Updated

The virtual memory management system in FreeBSD 4.5-RELEASE and earlier does not properly check the existence of a VM object during page invalidation, which allows local users to cause a denial of service (crash) by calling msync on an unaccessed memory map created with MAPANON and MAPNOSYNC flags.

Affected Software

2 affected components

FreeBSD FreeBSD=4.5-stable

FreeBSD FreeBSD=4.5-release

Remediation

Patch Available

ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-02:22.mmap.asc

Event History

Dec 31, 2002

CVE Published

05:00 AM

Jun 21, 2005

CVE Published

via MITRE·08:00 AM

Data Sourced

via MITRE·08:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2002-1667?

The severity of CVE-2002-1667 is classified as a denial of service vulnerability affecting FreeBSD 4.5-RELEASE and earlier.

How do I fix CVE-2002-1667?

To fix CVE-2002-1667, upgrade to a version of FreeBSD later than 4.5, as these versions contain patches that address this vulnerability.

Who is affected by CVE-2002-1667?

CVE-2002-1667 affects local users of FreeBSD 4.5-RELEASE and earlier systems.

What action can trigger CVE-2002-1667?

CVE-2002-1667 can be triggered by local users calling the msync function on an unaccessed memory map created with MAP_ANON and MAP_NOSYNC flags.

What are the potential consequences of CVE-2002-1667?

The potential consequences of CVE-2002-1667 include system crashes and denial of service due to improper virtual memory management.