# CVE-2024-10209: Incorrect Permission Assignment in APROL file system

> An authenticated local attacker can read and modify configuration files of other users in the APROL industrial automation system.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-xr74-5p74-mh9w

## What is CVE-2024-10209?

CVE-2024-10209 is a high-severity missing authorization vulnerability in B&R Industrial Automation GmbH APROL, published on 25 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Incorrect Permission Assignment for Critical Resource vulnerability in the file system used in B&R APROL <4.4-01 may allow an authenticated local attacker to read and alter the configuration of another engineering or runtime user.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2024-10209 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10209 is a high-severity missing authorization vulnerability in B&R Industrial Automation GmbH APROL, published on 25 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10209 in the wild and no public exploit code.

Affected product: B&R Industrial Automation GmbH APROL. 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-10209/ (Markdown: https://insights.sbomify.com/CVE-2024-10209/index.md)
```

## Sources

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

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