SUSE: 2020:1417-1 moderate: freetds

    Date 26 May 2020
    Posted By LinuxSecurity Advisories
    An update that fixes one vulnerability is now available.
       SUSE Security Update: Security update for freetds
    Announcement ID:    SUSE-SU-2020:1417-1
    Rating:             moderate
    References:         #1141132 
    Cross-References:   CVE-2019-13508
    Affected Products:
                        SUSE Linux Enterprise Module for Server Applications 15-SP1
       An update that fixes one vulnerability is now available.
       This update for freetds to 1.1.36 fixes the following issues:
       Security issue fixed:
       - CVE-2019-13508: Fixed a heap overflow that could have been caused by
         malicious servers sending UDT types over protocol version 5.0
       Non-security issues fixed:
       - Enabled Kerberos support
       - Version update to 1.1.36:
         * Default TDS protocol version is now "auto"
         * Improved UTF-8 performances
         * TDS Pool Server is enabled
         * MARS support is enabled
         * NTLMv2 is enabled
         * See NEWS and ChangeLog for a complete list of changes
    Patch Instructions:
       To install this SUSE Security Update use the SUSE recommended installation methods
       like YaST online_update or "zypper patch".
       Alternatively you can run the command listed for your product:
       - SUSE Linux Enterprise Module for Server Applications 15-SP1:
          zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP1-2020-1417=1
    Package List:
       - SUSE Linux Enterprise Module for Server Applications 15-SP1 (aarch64 ppc64le s390x x86_64):
    sle-security-updates mailing list
    This email address is being protected from spambots. You need JavaScript enabled to view it.

    LinuxSecurity Poll

    How do you feel about the elimination of the terms 'blacklist' and 'slave' from the Linux kernel?

    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":"112","title":"I strongly support this change - racially charged language should not be used in the code and documentation of the kernel and other open-source projects.","votes":"7","type":"x","order":"1","pct":18.42,"resources":[]},{"id":"113","title":"I'm indifferent - this small change will not affect broader issues of racial insensitivity and white privilege.","votes":"4","type":"x","order":"2","pct":10.53,"resources":[]},{"id":"114","title":"I'm opposed to this change - there is no need to change language that has been used for years. It doesn't make sense for people to take offense to terminology used in community projects.","votes":"27","type":"x","order":"3","pct":71.05,"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
    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.