CriticalCVE-2017-15041

    Go: security vulnerability (CVE-2017-15041)

    Published Sources: CVE.org, OSV

    What is affected, what to do

    Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution. Using custom domains, it is possible to arrange things so that example.com/pkg1 points to a Subversion repository but example.com/pkg1/pkg2 points to a Git repository.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Go lte *..1.8.3
    • Go eq 1.9..1.9
    • Debian Linux eq 9.0..9.0
    • Red Hat Developer Tools eq 1.0..1.0
    • Red Hat Enterprise Linux Extended Update Support (EUS) eq 7.6..7.6
    • Red Hat Enterprise Linux Extended Update Support (EUS) eq 7.7..7.7
    • Redhat Enterprise Linux Server eq 7.0..7.0
    • Redhat Enterprise Linux Server Advanced mission critical Update Support (AUS) eq 7.6..7.6
    • Redhat Enterprise Linux Server Advanced mission critical Update Support (AUS) eq 7.7..7.7
    • Red Hat Enterprise Linux (TUS) eq 7.6..7.6
    • Red Hat Enterprise Linux (TUS) eq 7.7..7.7

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

    Metrics

    9.8

    Priority

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

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, OSV

    9.3 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 95.4

    Show all metrics
    Severity
    Critical
    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
    121.73 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
    9.8 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
    9.8
    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
    9.3 %
    Moderate — model estimates 1-10% exploitation likelihood.
    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
    95.4
    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

    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

    Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution. Using custom domains, it is possible to arrange things so that example.com/pkg1 points to a Subversion repository but example.com/pkg1/pkg2 points to a Git repository. If the Subversion repository includes a Git checkout in its pkg2 directory and some other work is done to ensure the proper ordering of operations, "go get" can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository's Git checkout has malicious commands in .git/hooks/, they will execute on the system running "go get."

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

    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
    golanggo
    • ≤ 1.8.3
    • 1.9
    • —
    • —
    redhatdeveloper_tools
    • 1.0
    • —
    gotoolchain
    • 1.9.0-0
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebiandebian_linux9.0
    Linuxredhatenterprise_linux_eus7.6
    Linuxredhatenterprise_linux_eus7.7
    Linuxredhatenterprise_linux_server7.0
    Linuxredhatenterprise_linux_server_aus7.6
    Linuxredhatenterprise_linux_server_aus7.7
    Linuxredhatenterprise_linux_tus7.6
    Linuxredhatenterprise_linux_tus7.7

    References & sources

    • go.devcl/68110fix
    • go.googlesource.comgo/+/ec71ee078fd3243b78c0d404c8634bd97e38d7ebfix
    • go.devissue/22125report
    • groups.google.comg/golang-dev/c/RinSE3EiJBI/m/kYL7zb07AgAJweb
    • access.redhat.comRHSA-2017:3463Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • access.redhat.comRHSA-2018:0878Vendor advisory, x_refsource_REDHAT, Third-party advisory
    • golang.orgcl/68190x_refsource_CONFIRM, Issue tracking, Patch, Vendor advisory
    • securityfocus.com101196Vulnerability database, x_refsource_BID, Third-party advisory, Vulnerability database
    • golang.orgcl/68022x_refsource_CONFIRM, Issue tracking, Patch, Vendor advisory
    • security.gentoo.orgGLSA-201710-23Vendor advisory, x_refsource_GENTOO, Third-party advisory
    • groups.google.comd/msg/golang-dev/RinSE3EiJBI/kYL7zb07AgAJx_refsource_CONFIRM, Mailing list, Vendor advisory
    • github.comgolang/go/issues/22125x_refsource_CONFIRM, Issue tracking, Patch, 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-2017-15041
    <a href="https://intel.neosec.eu/en/cve/CVE-2017-15041"><img src="https://intel.neosec.eu/badge/cve/CVE-2017-15041.svg?lang=en" alt="CVE-2017-15041 – NEOSEC Intel" height="20"></a>