# CVE-2022-38355: Information disclosure in SVMPC1

> Unauthenticated attackers on the local network can access sensitive information stored by Daikin SVMPC1 and SVMPC2 controllers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-h927-jjxq-8g5v

## What is CVE-2022-38355?

CVE-2022-38355 is a high-severity vulnerability in Daikin SVMPC1 , published on 13 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Daikinlatam Svmpc1, Daikinlatam Svmpc2.

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

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

## Is CVE-2022-38355 being exploited?

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

## Other vulnerabilities in Daikin SVMPC1 

- [CVE-2022-41653](https://insights.sbomify.com/CVE-2022-41653/): Hardcoded credentials in SVMPC1 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38355 is a high-severity vulnerability in Daikin SVMPC1 , published on 13 Dec 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-38355 in the wild and no public exploit code.

Affected product: Daikin SVMPC1 . 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-38355/ (Markdown: https://insights.sbomify.com/CVE-2022-38355/index.md)
```

## Sources

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

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