CVE-2022-41653
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDaikin SVMPC1 version 2.1.22 and prior and SVMPC2 version 1.2.3 and prior are vulnerable to an attacker obtaining user login credentials and control the system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a credential theft vulnerability in Daikin's SVMPC1 and SVMPC2 HVAC management controller web interfaces. An attacker can obtain user login credentials, allowing unauthorized access to control the HVAC system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.1.22<= 1.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Daikin SVMPC controller on the networkScan network for devices running the SVMPC1 or SVMPC2 web management interface (typically port 80/443). Check device inventory or network scans for Daikin HVAC management controllers.Affected if A Daikin SVMPC1 or SVMPC2 controller is present on the network with its web interface accessible.
-
Check SVMPC1 firmware versionLog into the SVMPC1 web interface or check the device firmware/version information page. Look for a version number displayed as Svmpc1 or firmware version.Affected if The installed version is 2.1.22 or lower.
-
Check SVMPC2 firmware versionLog into the SVMPC2 web interface or check the device firmware/version information page. Look for a version number displayed as Svmpc2 or firmware version.Affected if The installed version is 1.2.3 or lower.
-
Verify web interface exposureConfirm the SVMPC web management interface is reachable from network segments that contain untrusted devices. Check firewall rules and access control lists protecting the device.Affected if The web interface is accessible from untrusted network segments rather than only from a dedicated management VLAN.
A user is affected if they have a Daikin SVMPC1 (version 2.1.22 or lower) or SVMPC2 (version 1.2.3 or lower) controller with its web interface exposed to the network where the vulnerability can be exploited.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to the SVMPC1/SVMPC2 management interfaces to trusted IPs only using firewall rules or network segmentation, and apply vendor patches when released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-41653 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data