CVE-2002-0973: Medium severity FreeBSD FreeBSD vulnerability

Published Aug 23, 2002
·
Updated

Integer signedness error in several system calls for FreeBSD 4.6.1 RELEASE-p10 and earlier may allow attackers to access sensitive kernel memory via large negative values to the (1) accept, (2) getsockname, and (3) getpeername system calls, and the (4) vesa FBIOGETPALETTE ioctl.

Affected Software

18 affected components
FreeBSD FreeBSD=4.1.1-stable
FreeBSD FreeBSD=4.1.1-release
FreeBSD FreeBSD=4.4-stable
FreeBSD FreeBSD=4.6-release
FreeBSD FreeBSD=4.3-stable
FreeBSD FreeBSD=4.5-stable
FreeBSD FreeBSD=4.5-release
FreeBSD FreeBSD=4.3-release
FreeBSD FreeBSD=4.2-stable
FreeBSD FreeBSD=4.5
FreeBSD FreeBSD=4.1
FreeBSD FreeBSD=4.4
FreeBSD FreeBSD=4.2
FreeBSD FreeBSD=4.0
FreeBSD FreeBSD=4.1.1
FreeBSD FreeBSD=4.6
FreeBSD FreeBSD=4.3
FreeBSD FreeBSD=4.6.1-release_p10

Event History

Aug 23, 2002
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2002-0973?

CVE-2002-0973 has a high severity level due to potential access to sensitive kernel memory by attackers.

2

How do I fix CVE-2002-0973?

To fix CVE-2002-0973, upgrade to a patched version of FreeBSD that addresses the signedness error.

3

What systems are affected by CVE-2002-0973?

CVE-2002-0973 affects FreeBSD versions 4.6.1 RELEASE-p10 and earlier.

4

What actions can be taken to mitigate CVE-2002-0973?

Mitigation for CVE-2002-0973 includes applying security patches and conducting regular vulnerability assessments.

5

Can CVE-2002-0973 be exploited remotely?

Yes, CVE-2002-0973 can potentially be exploited remotely through specific system calls.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203