All Vulnerability Reports

USN-4360-4: json-c vulnerability


Severity

Medium

Vendor

Canonical Ubuntu

Versions Affected

  • Canonical Ubuntu 14.04
  • Canonical Ubuntu 16.04
  • Canonical Ubuntu 18.04

Description

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.

CVEs contained in this USN include: CVE-2020-12762

Affected VMware Products and Versions

Severity is medium unless otherwise noted.

Vulnerable Cloud Foundry components individually listed here.

Impacted stemcells may be updated independently of upgrading Tanzu Application Service or Isolation Segment.

  • Isolation Segment
    • 2.7.x versions prior to 2.7.18
    • 2.8.x versions prior to 2.8.12
    • 2.9.x versions prior to 2.9.6
  • Operations Manager
    • 2.7.x versions prior to 2.7.19
    • 2.8.x versions prior to 2.8.10
    • 2.9.x versions prior to 2.9.6
  • Tanzu Greenplum for Kubernetes
    • All versions prior to 2.0.0
  • VMware Tanzu Application Service for VMs
    • 2.7.x versions prior to 2.7.18
    • 2.8.x versions prior to 2.8.12
    • 2.9.x versions prior to 2.9.6

Mitigation

The Cloud Foundry security team recommends upgrading the affected OSS components listed here if applicable. Upgrade VMware Tanzu products that use earlier versions of CF components to new Tanzu releases using new versions linked above. On the Tanzu Network product page for each release, check the Depends On section and/or Release Notes for this information. Releases that have fixed this issue include:

  • Isolation Segment
    • 2.7.18
    • 2.8.12
    • 2.9.6
  • Operations Manager
    • 2.7.19
    • 2.8.10
    • 2.9.6
  • Tanzu Greenplum for Kubernetes
    • 2.0.0
  • VMware Tanzu Application Service for VMs
    • 2.7.18
    • 2.8.12
    • 2.9.6

References

History

2020-05-28: Initial vulnerability report published.