CVE-2003-0859

mediumPriorität · verfolgen · 20EPSS 0.004 · 32. PerzentilEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.38% (32nd) EPSS
CVSS 4.9 · medium
Is it mine?
18 products
Prüfe deine Angriffsfläche
Who says so?
3 sources
enisa_euvd · nvd · redhat_csaf

EPSS · bewertet 2026-10-27

The getifaddrs function in GNU libc (glibc) 2.2.4 and earlier allows local users to cause a denial of service by sending spoofed messages as other users to the kernel netlink interface.

01

Behebungen

Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.

Ein Hersteller-Fix ist verfügbar.

  • BehobenRed Hat Linux 7.1redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run the following command at a shell prompt: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. On the i686 architecture, *.i686.rpm packages should be installed where available rather than *.i386.rpm. If you are unsure which architecture you are on, run the following command at a shell prompt: rpm -q --qf '%{arch}\n' glibc Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt

    https://access.redhat.com/errata/RHSA-2003:325
  • BehobenRed Hat Linux 7.2redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run the following command at a shell prompt: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. On the i686 architecture, *.i686.rpm packages should be installed where available rather than *.i386.rpm. If you are unsure which architecture you are on, run the following command at a shell prompt: rpm -q --qf '%{arch}\n' glibc Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt

    https://access.redhat.com/errata/RHSA-2003:325
  • BehobenRed Hat Linux 7.3redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run the following command at a shell prompt: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. On the i686 architecture, *.i686.rpm packages should be installed where available rather than *.i386.rpm. If you are unsure which architecture you are on, run the following command at a shell prompt: rpm -q --qf '%{arch}\n' glibc Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt

    https://access.redhat.com/errata/RHSA-2003:325
  • BehobenRed Hat Linux 8.0redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run the following command at a shell prompt: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. On the i686 architecture, *.i686.rpm packages should be installed where available rather than *.i386.rpm. If you are unsure which architecture you are on, run the following command at a shell prompt: rpm -q --qf '%{arch}\n' glibc Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt

    https://access.redhat.com/errata/RHSA-2003:325
  • BehobenRed Hat Linux 9redhat_csaf

    Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run the following command at a shell prompt: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. On the i686 architecture, *.i686.rpm packages should be installed where available rather than *.i386.rpm. If you are unsure which architecture you are on, run the following command at a shell prompt: rpm -q --qf '%{arch}\n' glibc Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. If up2date fails to connect to Red Hat Network due to SSL Certificate Errors, you need to install a version of the up2date client with an updated certificate. The latest version of up2date is available from the Red Hat FTP site and may also be downloaded directly from the RHN website: https://rhn.redhat.com/help/latest-up2date.pxt

    https://access.redhat.com/errata/RHSA-2003:325
02

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

4.9
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen

v2.04.9mediumAV:L/AC:L/Au:N/C:N/I:N/A:Cprimary · NVD / NIST USAusnutzbarkeit 3.9 · Auswirkung 6.9
v2.04.2mediumAV:L/AC:L/Au:N/C:N/I:N/A:C/E:Usecondary · CVSS-BT (t0sche)
03

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

CWE-354USLLM-abgeleitetCWE-400USLLM-abgeleitet
04

betroffene Produkte (18)

Betroffene Produkte und Versionsbereiche.

05

Advisories (1)

Hersteller- und Ökosystem-Meldungen dazu.

  • RHSA-2003:325Red Hat Security Advisory: : Updated glibc packages provide security and bug fixes2003-11-12csaf · redhat_csafUS

    Updated glibc packages that resolve vulnerabilities and address several bugs are now available.

06

auch bekannt als (2)

Weitere Namen und Kennungen dieser Entität.

07

quellen

Welche Quellen diesen Datensatz belegen und wann.

veröffentlicht 2003-12-15geändert 2026-06-16
08

Referenzen (6)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan