dbcve.org
Svmpc1Application · Daikinlatam

CVE-2022-38355

MEDIUM · 5.5 CVSS v3.1 Published 2022-12-13
Fix available
A fix is available. Upgrade to after 2.1.22 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Daikin SVMPC1 version 2.1.22 and prior and SVMPC2 version 1.2.3 and prior are vulnerable to attackers with access to the local area network (LAN) to disclose sensitive information stored by the affected product without requiring authentication.

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 confidence

Daikin SVMPC1 (versions 2.1.22 and prior) and SVMPC2 (versions 1.2.3 and prior) contain an unauthenticated information disclosure vulnerability. Attackers with access to the local area network can retrieve sensitive information stored by these HVAC controller products without any authentication credentials.

MitigationRestrict network access to the affected devices using network segmentation and firewall rules to limit exposure to trusted personnel only. Apply vendor patches when available to implement proper authentication for sensitive data access.

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
Svmpc1Application
Affected:<= 2.1.22
Svmpc2Application
Affected:<= 1.2.3

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Daikin HVAC controller on the network
    Scan your network for devices with the product name 'SVMPC1' or 'SVMPC2', or look for Daikin HVAC controllers using network discovery tools (nmap, network scans). Check device inventory or documentation for Daikin SVMPC1/SVMPC2 controllers.
    Affected if A Daikin SVMPC1 or SVMPC2 controller exists on your network
  2. Determine the SVMPC1 firmware version
    Access the device web interface or check the device management console for the firmware version. The version is typically displayed in the device settings, about page, or system information section.
    Affected if The firmware version is 2.1.22 or lower
  3. Determine the SVMPC2 firmware version
    Access the device web interface or check the device management console for the firmware version. The version is typically displayed in the device settings, about page, or system information section.
    Affected if The firmware version is 1.2.3 or lower
  4. Verify network accessibility without authentication
    Attempt to access sensitive endpoints on the device (such as configuration or data retrieval endpoints) from an untrusted network segment without providing any credentials. Use a tool like curl or a browser to send HTTP requests to common device ports.
    Affected if The device responds to requests from untrusted network segments without requiring authentication

You are affected if you have a Daikin SVMPC1 (firmware <= 2.1.22) or SVMPC2 (firmware <= 1.2.3) controller accessible on your network without proper network segmentation or authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.1.22
Interim mitigation

Restrict network access to the affected devices using network segmentation and firewall rules to limit exposure to trusted personnel only. Apply vendor patches when available to implement proper authentication for sensitive data access.

Recommended fix Moderate confidence

Latest available version from Daikin (newer than 2.1.22 for SVMPC1, newer than 1.2.3 for SVMPC2)

  1. 1. Identify the specific Daikin SVMPC1 or SVMPC2 device model and current firmware version
  2. 2. Contact Daikin technical support or check their official firmware download page for available updates
  3. 3. Download the latest firmware version from Daikin's official source
  4. 4. Follow Daikin's documented firmware update procedure for your specific device model
  5. 5. After updating, verify the device is no longer exposing sensitive information without authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Svmpc1 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38355 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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