# CVE-2024-51417: Property reflection in System.Linq.Dynamic.Core

> Attackers can access restricted reflection properties and static fields in System.Linq.Dynamic.Core, leading to unauthorized data exposure.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jan 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-4cv2-4hjh-77rx

## What is CVE-2024-51417?

CVE-2024-51417 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in System.Linq.Dynamic.Core before 1.6.0 allows remote access to properties on reflection types and static properties/fields.

Weakness: CWE-863 (Incorrect Authorization)

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

2 open source packages ship an affected version, including System.Linq.Dynamic.Core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `System.Linq.Dynamic.Core` | NuGet | All versions | 1.6.0 |
| `System.Linq.Dynamic.Core` | NuGet | All versions | 1.6.0 |

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

Upgrade System.Linq.Dynamic.Core to 1.6.0 or later.

## Is CVE-2024-51417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51417 is a medium-severity missing authorization vulnerability in n/a, published on 21 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51417 exists.

Affected packages and fixed versions:
- System.Linq.Dynamic.Core (NuGet): affected all versions; fixed in 1.6.0
- System.Linq.Dynamic.Core (NuGet): affected all versions; fixed in 1.6.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-51417/ (Markdown: https://insights.sbomify.com/CVE-2024-51417/index.md)
```

## Sources

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

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