Linux Security
    Linux Security
    Linux Security

    SUSE: 2020:2060-1 important: rubygem-puma

    Posted By
    An update that fixes four vulnerabilities is now available.
       SUSE Security Update: Security update for rubygem-puma
    Announcement ID:    SUSE-SU-2020:2060-1
    Rating:             important
    References:         #1158675 #1165402 #1172175 #1172176 
    Cross-References:   CVE-2019-16770 CVE-2020-11076 CVE-2020-11077
    Affected Products:
                        SUSE OpenStack Cloud 6-LTSS
       An update that fixes four vulnerabilities is now available.
       This update for rubygem-puma fixes the following issues:
       - Add patches for disabling TLSv1.0 and TLSv1.1 (jsc#SLE-6965):
       - Add CVE-2020-11077.patch (bsc#1172175, CVE-2020-11077)
       - Add CVE-2020-11076.patch (bsc#1172176, CVE-2020-11076)
       - Add CVE-2020-5247.patch (bsc#1165402) "Fixes a problem where we were not
         splitting newlines in headers according to Rack spec" The patch is
         reduced compared to the upstream version, which was patching also the
         parts that are not implemented in our old Puma version. This applies to
         unit test as well.
       - Add CVE-2019-16770.patch (bsc#1158675, SOC-10999, CVE-2019-16770) This
         patch fixes a DoS vulnerability a malicious client could use to block a
         large amount of threads.
    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 OpenStack Cloud 6-LTSS:
          zypper in -t patch SUSE-OpenStack-Cloud-6-LTSS-2020-2060=1
    Package List:
       - SUSE OpenStack Cloud 6-LTSS (x86_64):
    sle-security-updates mailing list
    This email address is being protected from spambots. You need JavaScript enabled to view it.

    LinuxSecurity Poll

    Which aspect of server security are you most interested in learning more about?

    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":"131","title":"Preventing information leakage","votes":"1","type":"x","order":"1","pct":100,"resources":[]},{"id":"132","title":"Firewall considerations","votes":"0","type":"x","order":"2","pct":0,"resources":[]},{"id":"133","title":"Permissions ","votes":"0","type":"x","order":"3","pct":0,"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.