# CVE-2018-8479: Security feature bypass in C SDK

> Attackers can spoof Azure IoT Device Provisioning requests via HTTP on Windows, bypassing security checks in the C SDK library.

- **Severity:** Medium 5.6 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c7cx-rfw4-4w69

## What is CVE-2018-8479?

CVE-2018-8479 is a medium-severity vulnerability in Microsoft C SDK, published on 13 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A spoofing vulnerability exists for the Azure IoT Device Provisioning for the C SDK library using the HTTP protocol on Windows platform, aka "Azure IoT SDK Spoofing Vulnerability." This affects C SDK.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 2 products.


Products: Microsoft C Software Development Kit, Microsoft Java Software Development Kit.

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

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

## Is CVE-2018-8479 being exploited?

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

## Other vulnerabilities in Microsoft C SDK

- [CVE-2018-8119](https://insights.sbomify.com/CVE-2018-8119/): Security feature bypass in C SDK (medium 5.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8479 is a medium-severity vulnerability in Microsoft C SDK, published on 13 Sep 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-8479 in the wild and no public exploit code.

Affected product: Microsoft C SDK. 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-8479/ (Markdown: https://insights.sbomify.com/CVE-2018-8479/index.md)
```

## Sources

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

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