# CVE-2022-33321: Information disclosure in Air Conditioning MFZ-GXT50/60/73VFK

> Remote attackers can sniff cleartext Basic Authentication credentials to disclose information or cause denial of service in Mitsubishi Electric consumer electronics.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-xxp6-vwcq-7x73

## What is CVE-2022-33321?

CVE-2022-33321 is a critical vulnerability in Mitsubishi Electric Corporation Air Conditioning MFZ-GXT50/60/73VFK, published on 8 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cleartext Transmission of Sensitive Information vulnerability due to the use of Basic Authentication for HTTP connections in Mitsubishi Electric consumer electronics products (PHOTOVOLTAIC COLOR MONITOR ECO-GUIDE, HEMS adapter, Wi-Fi Interface, Air Conditioning, Induction hob, Mitsubishi Electric HEMS Energy Measurement Unit, Refrigerator, Remote control with Wi-Fi Interface, BATHROOM THERMO VENTILATOR, Rice cooker, Mitsubishi Electric HEMS control adapter, Energy Recovery Ventilator, Smart Switch, Ventilating Fan, Range hood fan, Energy Measurement Unit and Air Purifier) allows a remote unauthenticated attacker to disclose information in the products or cause a denial of service (DoS) condition as a result by sniffing credential information (username and password).
The wide range of models/versions of Mitsubishi Electric consumer electronics products are affected by this vulnerability.
As for the affected product models/versions, see the Mitsubishi Electric's advisory which is listed in [References] section.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 178 products.


Products: Mitsubishielectric Ma-Ew85s-E Firmware, Mitsubishielectric Ma-Ew85s-Uk Firmware, Mitsubishielectric Mac-507if-E Firmware, Mitsubishielectric Mac-557if-E1 Firmware, Mitsubishielectric Mac-557if-E Firmware, Mitsubishielectric Mac-558if-E1 Firmware, Mitsubishielectric Mac-558if-E Firmware, Mitsubishielectric Mac-559if-E1 Firmware, Mitsubishielectric Mac-559if-E Firmware, Mitsubishielectric Mac-566ifb-E Firmware, Mitsubishielectric Mac-567ifb-E Firmware, Mitsubishielectric Mac-567ifb2-E Firmware, Mitsubishielectric Mac-568if-E Firmware, Mitsubishielectric Mac-568ifb-E Firmware, Mitsubishielectric Mac-568ifb2-E Firmware, Mitsubishielectric Mac-568ifb3-E Firmware, Mitsubishielectric Mac-576if-E1 Firmware, Mitsubishielectric Mac-587if-E Firmware, Mitsubishielectric Mac-587if2-E Firmware, Mitsubishielectric Mac-588if-E Firmware and 158 more.

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

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

## Is CVE-2022-33321 being exploited?

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

## Other vulnerabilities in Mitsubishi Electric Corporation Air Conditioning MFZ-GXT50/60/73VFK

- [CVE-2022-33322](https://insights.sbomify.com/CVE-2022-33322/): Cross-site scripting in Air Conditioning MFZ-GXT50/60/73VFK (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33321 is a critical vulnerability in Mitsubishi Electric Corporation Air Conditioning MFZ-GXT50/60/73VFK, published on 8 Nov 2022. 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-2022-33321 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation Air Conditioning MFZ-GXT50/60/73VFK. 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-33321/ (Markdown: https://insights.sbomify.com/CVE-2022-33321/index.md)
```

## Sources

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

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