# CVE-2023-45312: MTProto proxy remote code execution vulnerability

> A low-privileged remote attacker can bypass authentication in the default Erlang MTProto proxy installation to achieve remote command execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-738q-mc72-2q22

## What is CVE-2023-45312?

CVE-2023-45312 is a high-severity authentication bypass vulnerability in n/a, published on 10 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the mtproto_proxy (aka MTProto proxy) component through 0.7.2 for Erlang, a low-privileged remote attacker can access an improperly secured default installation without authenticating and achieve remote command execution ability.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2023-45312?

2 open source packages ship an affected version, including mtproto_proxy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mtproto_proxy` | Hex | All versions to 0.7.2 | None |
| `mtproto_proxy` | Hex | All versions to 0.7.2 | None |

Products: Mtproto Mt Proto Proxy.

## How do I fix CVE-2023-45312?

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

## Is CVE-2023-45312 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45312 and fix it if it is affected.

What it is: CVE-2023-45312 is a high-severity authentication bypass vulnerability in n/a, published on 10 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45312 in the wild and no public exploit code.

Affected packages and fixed versions:
- mtproto_proxy (Hex): affected all versions up to 0.7.2; no fix listed
- mtproto_proxy (Hex): affected all versions up to 0.7.2; no fix listed

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-2023-45312/ (Markdown: https://insights.sbomify.com/CVE-2023-45312/index.md)
```

## Sources

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

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