# CVE-2024-44930: Serilog Client IP Spoofing vulnerability

> Attackers can spoof client IP addresses in logs by manipulating HTTP headers, compromising audit trails and security controls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-5x5q-cqf6-gj8r

## What is CVE-2024-44930?

CVE-2024-44930 is a medium-severity vulnerability in n/a, published on 29 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Serilog before v2.1.0 was discovered to contain a Client IP Spoofing vulnerability, which allows attackers to falsify their IP addresses by specifying an arbitrary IP as a value of X-Forwarded-For or Client-Ip headers while performing HTTP requests.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including Serilog.Enrichers.ClientInfo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Serilog.Enrichers.ClientInfo` | NuGet | All versions | 2.1.0 |
| `Serilog.Enrichers.ClientInfo` | NuGet | All versions | 2.1.0 |

Products: Serilog-Contrib Serilog-Enrichers-Clientinfo.

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

Upgrade Serilog.Enrichers.ClientInfo to 2.1.0 or later.

## Is CVE-2024-44930 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44930 is a medium-severity vulnerability in n/a, published on 29 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-44930 in the wild and no public exploit code.

Affected packages and fixed versions:
- Serilog.Enrichers.ClientInfo (NuGet): affected all versions; fixed in 2.1.0
- Serilog.Enrichers.ClientInfo (NuGet): affected all versions; fixed in 2.1.0

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

## Sources

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

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