# CVE-2022-48422: Privilege escalation in n/a

> Local attackers can gain privileges by placing a malicious library in the working directory of ONLYOFFICE Docs on Linux.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Mar 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-j9xq-95fc-pqv2

## What is CVE-2022-48422?

CVE-2022-48422 is a high-severity vulnerability in n/a, published on 19 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

ONLYOFFICE Docs through 7.3 on certain Linux distributions allows local users to gain privileges via a Trojan horse libgcc_s.so.1 in the current working directory, which may be any directory in which an ONLYOFFICE document is located.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Onlyoffice Document Server.

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

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

## Is CVE-2022-48422 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3199](https://insights.sbomify.com/CVE-2021-3199/): ONLYOFFICE Docs Server Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2023-30186](https://insights.sbomify.com/CVE-2023-30186/): Use after free in n/a (critical 9.8)
- [CVE-2023-30187](https://insights.sbomify.com/CVE-2023-30187/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-25830](https://insights.sbomify.com/CVE-2021-25830/): Code injection in n/a (critical 9.8)
- [CVE-2021-25831](https://insights.sbomify.com/CVE-2021-25831/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48422 is a high-severity vulnerability in n/a, published on 19 Mar 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-48422 in the wild and no public exploit code.

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

## Sources

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

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