CVE-2003-0573: Medium severity SGI IRIX vulnerability
Published Aug 18, 2003
·Updated
The DNS callbacks in nsd in SGI IRIX 6.5.x through 6.5.20f, and possibly earlier versions, do not perform sufficient sanity checking, with unknown impact.
Affected Software
26 affected components
SGI IRIX=6.5.1
SGI IRIX=6.5.2
SGI IRIX=6.5.3
SGI IRIX=6.5.4
SGI IRIX=6.5.5
SGI IRIX=6.5.6
SGI IRIX=6.5.7
SGI IRIX=6.5.8
SGI IRIX=6.5.9
SGI IRIX=6.5.10
SGI IRIX=6.5.11
SGI IRIX=6.5.12
SGI IRIX=6.5.13
SGI IRIX=6.5.14
SGI IRIX=6.5.15f
SGI IRIX=6.5.15m
SGI IRIX=6.5.16f
SGI IRIX=6.5.16m
SGI IRIX=6.5.17f
SGI IRIX=6.5.17m
SGI IRIX=6.5.18f
SGI IRIX=6.5.18m
SGI IRIX=6.5.19f
SGI IRIX=6.5.19m
SGI IRIX=6.5.20f
SGI IRIX=6.5.20m
Remediation
Event History
Aug 18, 2003
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description
Data Sourced
via NVD·04:00 AM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What are the affected versions for CVE-2003-0573?
CVE-2003-0573 affects SGI IRIX versions 6.5.1 through 6.5.20f.
2
What is the nature of the vulnerability described in CVE-2003-0573?
CVE-2003-0573 involves insufficient sanity checking in the DNS callbacks of nsd on SGI IRIX.
3
What impact can CVE-2003-0573 have on the system?
The specific impact of CVE-2003-0573 is unknown, but it may lead to various security risks.
4
How can I mitigate CVE-2003-0573?
To mitigate CVE-2003-0573, it is recommended to upgrade to a patched version of SGI IRIX.
5
Is CVE-2003-0573 considered a critical vulnerability?
The severity of CVE-2003-0573 has not been explicitly stated, but it should be addressed to prevent potential exploitation.