Ubuntu 4360-4: json-c vulnerability

    Date 28 May 2020
    Posted By LinuxSecurity Advisories
    json-c could be made to execute arbitrary code if it received a specially crafted JSON file.
    Ubuntu Security Notice USN-4360-4
    May 28, 2020
    json-c vulnerability
    A security issue affects these releases of Ubuntu and its derivatives:
    - Ubuntu 20.04 LTS
    - Ubuntu 19.10
    - Ubuntu 18.04 LTS
    - Ubuntu 16.04 LTS
    - Ubuntu 14.04 ESM
    - Ubuntu 12.04 ESM
    json-c could be made to execute arbitrary code if it received
    a specially crafted JSON file.
    Software Description:
    - json-c: JSON manipulation library
    USN-4360-1 fixed a vulnerability in json-c. The security fix introduced a
    memory leak that was reverted in USN-4360-2 and USN-4360-3. This update provides
    the correct fix update for CVE-2020-12762.
    Original advisory details:
     It was discovered that json-c incorrectly handled certain JSON files.
     An attacker could possibly use this issue to execute arbitrary code.
    Update instructions:
    The problem can be corrected by updating your system to the following
    package versions:
    Ubuntu 20.04 LTS:
      libjson-c4                      0.13.1+dfsg-7ubuntu0.3
    Ubuntu 19.10:
      libjson-c4                      0.13.1+dfsg-4ubuntu0.3
    Ubuntu 18.04 LTS:
      libjson-c3                      0.12.1-1.3ubuntu0.3
    Ubuntu 16.04 LTS:
      libjson-c2                      0.11-4ubuntu2.6
      libjson0                        0.11-4ubuntu2.6
    Ubuntu 14.04 ESM:
      libjson-c2                      0.11-3ubuntu1.2+esm3
      libjson0                        0.11-3ubuntu1.2+esm3
    Ubuntu 12.04 ESM:
      libjson0                        0.9-1ubuntu1.4
    In general, a standard system update will make all the necessary changes.
    Package Information:

    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.