USN-3968-1: Sudo vulnerabilities

23795

14 November 2019

14 November 2019

CLOSED

MEDIUM

CVE-2016-7076,CVE-2017-1000368

Severity

Medium

Vendor

Canonical Ubuntu

Versions Affected

  • Canonical Ubuntu 16.04

Description

Florian Weimer discovered that Sudo incorrectly handled the noexec restriction when used with certain applications. A local attacker could possibly use this issue to bypass configured restrictions and execute arbitrary commands. (CVE-2016-7076)

It was discovered that Sudo did not properly parse the contents of /proc/[pid]/stat when attempting to determine its controlling tty. A local attacker in some configurations could possibly use this to overwrite any file on the filesystem, bypassing intended permissions. (CVE-2017-1000368)

CVEs contained in this USN include: CVE-2016-7076, CVE-2017-1000368

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 Pivotal Application Service, Pivotal Container Service, or PCF Isolation Segment.
  • Pivotal Application Service
    • 2.5.x versions prior to 2.5.5
    • 2.4.x versions prior to 2.4.9
    • 2.3.x versions prior to 2.3.13
  • PCF Isolation Segment
    • 2.5.x versions prior to 2.5.5
    • 2.4.x versions prior to 2.4.10
    • 2.3.x versions prior to 2.3.13
  • Pivotal Operations Manager
    • 2.5.x versions prior to 2.5.4
    • 2.4.x versions prior to 2.4.11
    • 2.3.x versions prior to 2.3.18
  • PCF Container Service
    • 1.3.x versions prior to 1.3.7
    • 1.4.x versions prior to 1.4.2
  • Pivotal Greenplum for Kubernetes
    • All versions prior to 1.2.0

Mitigation

Users of affected products are strongly encouraged to follow one of the mitigations below. The Cloud Foundry security team recommends upgrading BOSH to the affected OSS components listed here if applicable. Upgrade Pivotal products that use earlier versions of CF components to new Pivotal releases using new versions linked above. On the Pivotal 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:
  • Pivotal Application Service
    • 2.5.5
    • 2.4.9
    • 2.3.13
  • PCF Isolation Segment
    • 2.5.5
    • 2.4.10
    • 2.3.13
  • Pivotal Operations Manager
    • 2.5.4
    • 2.4.11
    • 2.3.18
  • Pivotal Container Service
    • 1.3.7
    • 1.4.2
  • Pivotal Greenplum for Kubernetes:
    • 1.2.0

References