# CVE-2022-4768: Dropbox merou SSH Public Key public_key.py add_public_key injection

> Remote attackers can inject commands via the SSH public key argument in Dropbox merou, potentially leading to code execution.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-r4w8-5mfm-rhh8

## What is CVE-2022-4768?

CVE-2022-4768 is a medium-severity command injection vulnerability in Dropbox merou, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in Dropbox merou. It has been classified as critical. Affected is the function add_public_key of the file grouper/public_key.py of the component SSH Public Key Handler. The manipulation of the argument public_key_str leads to injection. It is possible to launch the attack remotely. The name of the patch is d93087973afa26bc0a2d0a5eb5c0fde748bdd107. It is recommended to apply a patch to fix this issue. VDB-216906 is the identifier assigned to this vulnerability.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Dropbox Merou.

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

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

## Is CVE-2022-4768 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4768 is a medium-severity command injection vulnerability in Dropbox merou, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4768 in the wild and no public exploit code.

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

## Sources

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

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