# CVE-2022-4311: Information disclosure in PcVue

> Attackers with log file access can discover sensitive connection strings and credentials, enabling unauthorized access to underlying data sources in PcVue.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/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-fjxv-6346-8j89

## What is CVE-2022-4311?

CVE-2022-4311 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

An insertion of sensitive information into log file vulnerability exists in PcVue versions 15 through 15.2.2. This
could allow a user with access to the log files to discover connection strings of data sources configured for the
DbConnect, which could include credentials. Successful exploitation of this vulnerability could allow other users
unauthorized access to the underlying data sources.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Arcinfo Pcvue.

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

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

## Is CVE-2022-4311 being exploited?

There is no known exploitation of CVE-2022-4311 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-4311 and fix it if it is affected.

What it is: CVE-2022-4311 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-4311 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-4311/ (Markdown: https://insights.sbomify.com/CVE-2022-4311/index.md)
```

## Sources

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

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