# CVE-2018-1267: Missing authorization in n/a

> Improper access control in Cloud Foundry Silk CNI allows applications to bypass routing policies and reach other applications on the network.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7g7m-r288-q7h8

## What is CVE-2018-1267?

CVE-2018-1267 is a high-severity missing authorization vulnerability in n/a, published on 27 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloud Foundry Silk CNI plugin, versions prior to 0.2.0, contains an improper access control vulnerability. If the platform is configured with an application security group (ASG) that overlaps with the Silk overlay network, any applications can reach any other application on the network regardless of the configured routing policies.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2018-1267?

It affects 1 product.


Products: Cloudfoundry Silk-Release.

## How do I fix CVE-2018-1267?

No fix has been published for CVE-2018-1267 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1267 being exploited?

There is no known exploitation of CVE-2018-1267 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1267 and fix it if it is affected.

What it is: CVE-2018-1267 is a high-severity missing authorization vulnerability in n/a, published on 27 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1267 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1267/ (Markdown: https://insights.sbomify.com/CVE-2018-1267/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1267
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1267
- OSV: https://osv.dev/vulnerability/CVE-2018-1267

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1267/
Summaries are generated and may contain mistakes; the official description above is the record.