Mageia 2020-0232: dojo security update

    Date 27 May 2020
    208
    Posted By LinuxSecurity Advisories
    Advisory text to describe the update. Wrap lines at ~75 chars. Updated dojo package fixes security vulnerabilities: In affected versions of dojo, the deepCopy method is vulnerable to
    MGASA-2020-0232 - Updated dojo packages fix security vulnerability
    
    Publication date: 27 May 2020
    URL: https://advisories.mageia.org/MGASA-2020-0232.html
    Type: security
    Affected Mageia releases: 7
    CVE: CVE-2020-5258,
         CVE-2020-5259
    
    Advisory text to describe the update.
    Wrap lines at ~75 chars.
    Updated dojo package fixes security vulnerabilities:
    
    In affected versions of dojo, the deepCopy method is vulnerable to
    prototype Pollution. An attacker could manipulate these attributes
    to overwrite, or pollute, a JavaScript application object prototype
    of the base object by injecting other values (CVE-2020-5258).
    
    The Dojox jQuery wrapper jqMix mixin method is vulnerable to Prototype
    Pollution. An attacker could manipulate these attributes to overwrite, or
    pollute, a JavaScript application object prototype of the base object by
    injecting other values (CVE-2020-5259).
    
    References:
    - https://bugs.mageia.org/show_bug.cgi?id=26335
    - https://www.debian.org/lts/security/2020/dla-2139
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5258
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-5259
    
    SRPMS:
    - 7/core/dojo-1.14.6-1.mga7
    

    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).
    /main-polls/32-how-do-you-feel-about-the-elimination-of-the-terms-blacklist-and-slave-from-the-linux-kernel?task=poll.vote&format=json
    32
    radio
    [{"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.