CVE intelligence and bounded remediation
CVE-2022-33321 — Mitsubishielectric Mac-557If-E Firmware security vulnerability
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.
- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Published
- 2022-11-08
- CISA KEV
- Not currently listed
- Ecosystem
- operating-system
- Weaknesses
- CWE-319
Affected products
- mitsubishielectric / mac-557if-e_firmware
- mitsubishielectric / mac-557if-e1_firmware
- mitsubishielectric / pac-wf010-e_firmware
- mitsubishielectric / mac-566ifb-e_firmware
- mitsubishielectric / mac-576if-e1_firmware
- mitsubishielectric / mac-567ifb-e_firmware
Matched remediation archetype
Cryptography, certificate, signature, and channel validation
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
- Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
- Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.
Remediate safely
- Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
- Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
- Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.