HighCVE-2018-16873

    Golang: Improper Input Validation (CVE-2018-16873)

    Published Sources: CVE.org, OSV, SUSE

    What is affected, what to do

    In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get).

    Update go to version 1.10.6.

    Affected
    • Golang eq 1.10.6..1.10.6
    • Golang eq 1.11.3..1.11.3

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org, OSV, SUSE

    66.3 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.28

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    116.35 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    66.3 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.28
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-20

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u".

    Source: NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities), suse_csaf

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    [UNKNOWN]golang
    • 1.11.3
    • 1.10.6
    • —
    • —
    golanggo
    • < 1.10.6
    • 1.11.0 – < 1.11.3
    • 1.10.6
    • 1.11.3
    opensusebackports_sle
    • 15.0
    • —
    gotoolchain
    • 1.11.0-0
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebiandebian_linux9.0
    Linuxopensuseleap15.0
    Linuxopensuseleap15.1
    Linuxopensuseleap42.3
    Linuxsuselinux_enterprise_server12

    Weakness classes (CWE)

    • CWE-20Improper Input Validation

      Class

      The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

      Entry at MITRE CWE-20

    References & sources

    • go.devcl/154101fix
    • go.googlesource.comgo/+/bc82d7c7db83487e05d7a88e06549d4ae2a688c3fix
    • go.devissue/29230report
    • groups.google.comg/golang-announce/c/Kw31K8G7Fi0web
    • securityfocus.com106226Vulnerability database, x_refsource_BID, Third-party advisory, Vulnerability database
    • security.gentoo.orgGLSA-201812-09Vendor advisory, x_refsource_GENTOO, Mitigation, Third-party advisory
    • bugzilla.redhat.comshow_bug.cgi?id=CVE-2018-16873x_refsource_CONFIRM, Issue tracking, Third-party advisory
    • groups.google.comforum/?pli=1x_refsource_MISC
    • lists.opensuse.orgopenSUSE-SU-2019:1079Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgopenSUSE-SU-2019:1444Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgopenSUSE-SU-2019:1499Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgopenSUSE-SU-2019:1506Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgopenSUSE-SU-2019:1703Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.opensuse.orgopenSUSE-SU-2020:0554Vendor advisory, x_refsource_SUSE, Mailing list, Third-party advisory
    • lists.debian.org[debian-lts-announce] 20210313 [SECURITY] [DLA 2591-1] golang-1.7 security updateMailing list, x_refsource_MLIST, Mailing list, Third-party advisory
    • lists.debian.org[debian-lts-announce] 20210313 [SECURITY] [DLA 2592-1] golang-1.8 security updateMailing list, x_refsource_MLIST, Mailing list, Third-party advisory
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2018-16873
    <a href="https://intel.neosec.eu/en/cve/CVE-2018-16873"><img src="https://intel.neosec.eu/badge/cve/CVE-2018-16873.svg?lang=en" alt="CVE-2018-16873 – NEOSEC Intel" height="20"></a>