# CVE-2024-43613: Azure Database for PostgreSQL Flexible Server Extension Elevation of Privilege Vulnerability

> Attackers can elevate privileges within Azure Database for PostgreSQL Flexible Server extensions, potentially gaining unauthorized control over the database environment.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-mp4j-j99g-pqwf

## What is CVE-2024-43613?

CVE-2024-43613 is a high-severity vulnerability in Microsoft Azure Database for PostgreSQL Flexible Server, published on 12 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Azure Database for PostgreSQL Flexible Server Extension Elevation of Privilege Vulnerability

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-43613?

It affects 1 product.


Products: Microsoft Azure Database for Postgresql Flexible Server.

## How do I fix CVE-2024-43613?

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

## Is CVE-2024-43613 being exploited?

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

## Other vulnerabilities in Microsoft Azure Database for PostgreSQL Flexible Server

- [CVE-2024-49042](https://insights.sbomify.com/CVE-2024-49042/): Azure Database for PostgreSQL Flexible Server Extension Elevation of Privilege Vulnerability (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-43613 and fix it if it is affected.

What it is: CVE-2024-43613 is a high-severity vulnerability in Microsoft Azure Database for PostgreSQL Flexible Server, published on 12 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43613 in the wild and no public exploit code.

Affected product: Microsoft Azure Database for PostgreSQL Flexible 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-2024-43613/ (Markdown: https://insights.sbomify.com/CVE-2024-43613/index.md)
```

## Sources

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

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