How severe is CVE-2018-1227?

CVE-2018-1227 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2018-1227 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-1227?

CVE-2018-1227 affects Pivotal Software Concourse. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-1227?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2018-1227 published?

CVE-2018-1227 was published on 2018-03-13 and last updated on 2026-06-17.

CVE-2018-1227

CVE-2018-1227 is a high-severity vulnerability in Pivotal Software Concourse with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (65th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Pivotal Software Concourse
Published: 2018-03-13
Last modified: 2026-06-17

Description

Pivotal Concourse after 2018-03-05 might allow remote attackers to have an unspecified impact, if a customer obtained the Concourse software from a DNS domain that is no longer controlled by Pivotal. The original domain for the Concourse CI (concourse-dot-ci) open source project has been registered by an unknown actor, and is therefore no longer the official website for Concourse CI. The new official domain is concourse-ci.org. At approximately 4 am EDT on March 7, 2018 the Concourse OSS team began receiving reports that the Concourse domain was not responding. The Concourse OSS team discovered, upon investigation with both the original and the new domain registrars, that the originating domain registrar had made the domain available for purchase. This was done despite the domain being renewed by the Concourse OSS team through August 2018. For a customer to be affected, they would have needed to access a download from a "concourse-dot-ci" domain web site after March 6, 2018 18:00:00 EST. Accessing that domain is NOT recommended by Pivotal. Anyone who had been using that domain should immediately begin using the concourse-ci.org domain instead. Customers can also safely access Concourse software from the traditionally available locations on the Pivotal Network or GitHub.

Frequently asked questions

What is CVE-2018-1227?: Pivotal Concourse after 2018-03-05 might allow remote attackers to have an unspecified impact, if a customer obtained the Concourse software from a DNS domain that is no longer controlled by Pivotal. The original domain for the Concourse CI (concourse-dot-ci) open source project has been registered by an unknown actor, and is therefore no longer the official website for Concourse CI. The new official domain is concourse-ci.org. At approximately 4 am EDT on March 7, 2018 the Concourse OSS team began receiving reports that the Concourse domain was not responding. The Concourse OSS team discovered, upon investigation with both the original and the new domain registrars, that the originating domain registrar had made the domain available for purchase. This was done despite the domain being renewed by the Concourse OSS team through August 2018. For a customer to be affected, they would have needed to access a download from a "concourse-dot-ci" domain web site after March 6, 2018 18:00:00 EST. Accessing that domain is NOT recommended by Pivotal. Anyone who had been using that domain should immediately begin using the concourse-ci.org domain instead. Customers can also safely access Concourse software from the traditionally available locations on the Pivotal Network or GitHub.
How severe is CVE-2018-1227?: CVE-2018-1227 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2018-1227 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1227?: CVE-2018-1227 affects Pivotal Software Concourse. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-1227?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-1227 published?: CVE-2018-1227 was published on 2018-03-13 and last updated on 2026-06-17.

References

https://pivotal.io/security/cve-2018-1227

Affected products (1)

cpe:2.3:a:pivotal_software:concourse:*:*:*:*:*:*:*:*

More vulnerabilities in Pivotal Software Concourse

CVE-2020-5415 — Critical (CVSS 10.0): Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to…
CVE-2018-15798 — High (CVSS 7.6): Pivotal Concourse Release, versions 4.x prior to 4.2.2, login flow allows redirects to untrusted websites. A remote…
CVE-2019-3792 — Medium (CVSS 6.8): Pivotal Concourse version 5.0.0, contains an API that is vulnerable to SQL injection. An Concourse resource can craft a…
CVE-2020-5409 — Medium (CVSS 6.1): Pivotal Concourse, most versions prior to 6.0.0, allows redirects to untrusted websites in its login flow. A remote…
CVE-2022-31683 — Medium (CVSS 5.4): Concourse (7.x.y prior to 7.8.3 and 6.x.y prior to 6.7.9) contains an authorization bypass issue. A Concourse user can…
CVE-2019-3803 — Medium (CVSS 4.5): Pivotal Concourse, all versions prior to 4.2.2, puts the user access token in a url during the login flow. A remote…

All CVEs affecting Pivotal Software Concourse →