# CVE-2022-4312: Information disclosure in PcVue

> An attacker with file access can read cleartext SMTP credentials and SIM PINs from configuration files, leading to account compromise.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-6w7r-4v6h-jjq5

## What is CVE-2022-4312?

CVE-2022-4312 is a medium-severity vulnerability in ARC Informatique PcVue, published on 12 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A cleartext storage of sensitive information vulnerability exists in PcVue versions 8.10 through 15.2.3. This could
allow an unauthorized user with access the email and short messaging service (SMS) accounts configuration files
to discover the associated simple mail transfer protocol (SMTP) account credentials and the SIM card PIN code.
Successful exploitation of this vulnerability could allow an unauthorized user access to the underlying email
account and SIM card.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Arcinfo Pcvue.

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

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

## Is CVE-2022-4312 being exploited?

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

## Other vulnerabilities in ARC Informatique PcVue

- [CVE-2020-26867](https://insights.sbomify.com/CVE-2020-26867/): ARC Informatique PcVue Deserialization of Untrusted Data (critical 9.8)
- [CVE-2026-14868](https://insights.sbomify.com/CVE-2026-14868/): Weak encryption mechanism for User directory (high 8.4)
- [CVE-2020-26868](https://insights.sbomify.com/CVE-2020-26868/): ARC Informatique PcVue Access to Critical Private Variable via Public Method (high 7.5)
- [CVE-2020-26869](https://insights.sbomify.com/CVE-2020-26869/): ARC Informatique PcVue Exposure of Sensitive Information to an Unauthorized Actor (high 7.5)
- [CVE-2026-14867](https://insights.sbomify.com/CVE-2026-14867/): Insecure password storage in User directory (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4312 is a medium-severity vulnerability in ARC Informatique PcVue, published on 12 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4312 in the wild and no public exploit code.

Affected product: ARC Informatique PcVue. 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-4312/ (Markdown: https://insights.sbomify.com/CVE-2022-4312/index.md)
```

## Sources

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

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