# CVE-2022-43309: Misconfiguration in n/a

> Insecure permissions in Supermicro BMC firmware allow attackers to bypass security controls and potentially escalate privileges.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-x3g3-cjwm-fv45

## What is CVE-2022-43309?

CVE-2022-43309 is a medium-severity vulnerability in n/a, published on 7 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Supermicro X11SSL-CF HW Rev 1.01, BMC firmware v1.63 was discovered to contain insecure permissions.

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

## Which versions are affected by CVE-2022-43309?

It affects 146 products.


Products: Supermicro H11dsi-Nt Firmware, Supermicro H11dsi Firmware, Supermicro H11dst-B Firmware, Supermicro H11dsu-in Firmware, Supermicro H12dgo-6 Firmware, Supermicro H12dsg-O-Cpu Firmware, Supermicro H12dsi-N6 Firmware, Supermicro H12dsi-Nt6 Firmware, Supermicro H12dst-B Firmware, Supermicro H12dsu-in Firmware, Supermicro H12dsu-Inr Firmware, Supermicro H12ssff-An6 Firmware, Supermicro H12ssg-Anp6 Firmware, Supermicro H12ssl-C Firmware, Supermicro H12ssl-Ct Firmware, Supermicro H12ssl-I Firmware, Supermicro H12ssl-Nt Firmware, Supermicro H12sst-Ps Firmware, Supermicro H12ssw-in Firmware, Supermicro H12ssw-Inl Firmware and 126 more.

## How do I fix CVE-2022-43309?

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

## Is CVE-2022-43309 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34853](https://insights.sbomify.com/CVE-2023-34853/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43309 and fix it if it is affected.

What it is: CVE-2022-43309 is a medium-severity vulnerability in n/a, published on 7 Apr 2023. 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-2022-43309 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-2022-43309/ (Markdown: https://insights.sbomify.com/CVE-2022-43309/index.md)
```

## Sources

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

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