# CVE-2015-3229: Security feature bypass in n/a

> Attackers can intercept Fedora Atomic updates via HTTP, enabling man-in-the-middle attacks to modify system updates.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cg43-cf45-g8h6

## What is CVE-2015-3229?

CVE-2015-3229 is a medium-severity vulnerability in n/a, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fedora-cloud-atomic.ks in spin-kickstarts allows remote attackers to conduct man-in-the-middle attacks by leveraging use of HTTP to download Fedora Atomic updates.

Weakness: CWE-264

## Which versions are affected by CVE-2015-3229?

It affects 1 product.


Products: Fedoraproject Spin-Kickstarts.

## How do I fix CVE-2015-3229?

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

## Is CVE-2015-3229 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3229 and fix it if it is affected.

What it is: CVE-2015-3229 is a medium-severity vulnerability in n/a, published on 16 Oct 2017. 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-2015-3229 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-2015-3229/ (Markdown: https://insights.sbomify.com/CVE-2015-3229/index.md)
```

## Sources

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

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