# CVE-2021-33107: Hardcoded credentials in Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx

> Unauthenticated users with physical access can disclose information due to insufficiently protected credentials in Intel AMT SDK USB provisioning.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-343q-2m8h-67wf

## What is CVE-2021-33107?

CVE-2021-33107 is a medium-severity vulnerability in Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx, published on 9 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficiently protected credentials in USB provisioning for Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx before versions 11.0.0.0012, 12.0.0.0011, 14.0.0.0004 and 15.0.0.0004 may allow an unauthenticated user to potentially enable information disclosure via physical access.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2021-33107?

It affects 180 products.


Products: Intel Active Management Technology Software Development Kit, Intel Core I3-1000g1 Firmware, Intel Core I3-1000g4 Firmware, Intel Core I3-1000ng4 Firmware, Intel Core I3-1005g1 Firmware, Intel Core I3-10100 Firmware, Intel Core I3-10100e Firmware, Intel Core I3-10100f Firmware, Intel Core I3-10100t Firmware, Intel Core I3-10100te Firmware, Intel Core I3-10100y Firmware, Intel Core I3-10105 Firmware, Intel Core I3-10105f Firmware, Intel Core I3-10105t Firmware, Intel Core I3-10110u Firmware, Intel Core I3-10110y Firmware, Intel Core I3-10300 Firmware, Intel Core I3-10300t Firmware, Intel Core I3-10305 Firmware, Intel Core I3-10305t Firmware and 160 more.

## How do I fix CVE-2021-33107?

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

## Is CVE-2021-33107 being exploited?

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

## Other vulnerabilities in Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx

- [CVE-2022-26341](https://insights.sbomify.com/CVE-2022-26341/): Hardcoded credentials in Intel(R) AMT SDK, Intel(R) EMA and Intel(R) MC (high 8.2)
- [CVE-2020-12354](https://insights.sbomify.com/CVE-2020-12354/): Privilege escalation in Intel(R) AMT SDK (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-33107 and fix it if it is affected.

What it is: CVE-2021-33107 is a medium-severity vulnerability in Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx, published on 9 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-33107 in the wild and no public exploit code.

Affected product: Intel(R) AMT SDK before version 16.0.3, Intel(R) SCS before version 12.2 and Intel(R) MEBx. 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-2021-33107/ (Markdown: https://insights.sbomify.com/CVE-2021-33107/index.md)
```

## Sources

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

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