# CVE-2022-31014: SMTP Command Injection in iCalendar Attachments to emails via newlines in Nextcloud Server

> Attackers can inject SMTP commands via newlines in iCalendar attachments, hijacking email sessions to send unauthorized emails or modify sender details.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jul 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-264h-3v4w-6xh2

## What is CVE-2022-31014?

CVE-2022-31014 is a medium-severity command injection vulnerability in Nextcloud Nextcloud Server, published on 5 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Nextcloud server is an open source personal cloud server. Affected versions were found to be vulnerable to SMTP command injection. The impact varies based on which commands are supported by the backend SMTP server. However, the main risk here is that the attacker can then hijack an already-authenticated SMTP session and run arbitrary SMTP commands as the email user, such as sending emails to other users, changing the FROM user, and so on. As before, this depends on the configuration of the server itself, but newlines should be sanitized to mitigate such arbitrary SMTP command injection. It is recommended that the Nextcloud Server is upgraded to 22.2.8 , 23.0.5 or 24.0.1. There are no known workarounds for this issue.

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

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

It affects 1 product.


Products: Nextcloud Nextcloud Server.

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

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

## Is CVE-2022-31014 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31014 exists.

## Other vulnerabilities in Nextcloud Nextcloud Server

- [CVE-2021-32802](https://insights.sbomify.com/CVE-2021-32802/): Preview generation used third-party library not suited for user-generated content in Nextcloud server (critical 9.3)
- [CVE-2023-26482](https://insights.sbomify.com/CVE-2023-26482/): Scope of workflow operations is not validated in nextcloud server (critical 9.1)
- [CVE-2018-3775](https://insights.sbomify.com/CVE-2018-3775/): Auth bypass in Nextcloud Server (high 8.8)
- [CVE-2023-35172](https://insights.sbomify.com/CVE-2023-35172/): Nextcloud Server password reset endpoint is not brute force protected (high 8.7)
- [CVE-2023-32320](https://insights.sbomify.com/CVE-2023-32320/): Nextcloud Server's brute force protection allows someone to send more requests than intended (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31014 is a medium-severity command injection vulnerability in Nextcloud Nextcloud Server, published on 5 Jul 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31014 exists.

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

## Sources

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

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