Linux Security
    Linux Security
    Linux Security

    ArchLinux: 202012-17: unbound: denial of service

    Date 17 Dec 2020
    Posted By LinuxSecurity Advisories
    The package unbound before version 1.13.0-1 is vulnerable to denial of service.
    Arch Linux Security Advisory ASA-202012-17
    Severity: Low
    Date    : 2020-12-09
    CVE-ID  : CVE-2020-28935
    Package : unbound
    Type    : denial of service
    Remote  : No
    Link    :
    The package unbound before version 1.13.0-1 is vulnerable to denial of
    Upgrade to 1.13.0-1.
    # pacman -Syu "unbound>=1.13.0-1"
    The problem has been fixed upstream in version 1.13.0.
    NLnet Labs Unbound, up to and including version 1.12.0, and NLnet Labs
    NSD, up to and including version 4.3.3, contain a local vulnerability
    that would allow for a local symlink attack. When writing the PID file,
    Unbound and NSD create the file if it is not there, or open an existing
    file for writing. In case the file was already present, they would
    follow symlinks if the file happened to be a symlink instead of a
    regular file.
    An additional chown of the file would then take place after it was
    written, making the user Unbound/NSD is supposed to run as the new
    owner of the file.
    If an attacker has local access to the user Unbound/NSD runs as, she
    could create a symlink in place of the PID file pointing to a file that
    she would like to erase. If then Unbound/NSD is killed and the PID file
    is not cleared, upon restarting with root privileges, Unbound/NSD will
    rewrite any file pointed at by the symlink.
    This is a local vulnerability that could create a Denial of Service of
    the system Unbound/NSD is running on. It requires an attacker having
    access to the limited permission user Unbound/NSD runs as and point
    through the symlink to a critical file on the system.
    A local attacker might be able to cause a denial of service of the

    LinuxSecurity Poll

    'Tis the season of giving! How have you given back to the open-source community?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    [{"id":"171","title":"I've contributed to the development of an open-source project.","votes":"22","type":"x","order":"1","pct":34.92,"resources":[]},{"id":"172","title":"I've reviewed open-source code for security bugs.","votes":"13","type":"x","order":"2","pct":20.63,"resources":[]},{"id":"173","title":"I've made a donation to an open-source project.","votes":"28","type":"x","order":"3","pct":44.44,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350

    Please vote first in order to view vote results.


    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.