# CVE-2024-8313: Default or Guessable SNMP community names in B&R APROL

> Unauthenticated attackers can read and modify configuration via default SNMP community strings in B&R APROL industrial automation systems.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-4p64-jp2f-4r7g

## What is CVE-2024-8313?

CVE-2024-8313 is a high-severity 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 Exposure of Sensitive System Information to an Unauthorized Control Sphere and Initialization of a Resource with an Insecure Default vulnerability in the SNMP component of B&R APROL <4.4-00P5 may allow an unauthenticated adjacent-based attacker to read and alter configuration using SNMP.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2024-8313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8313 is a high-severity 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-8313 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-8313/ (Markdown: https://insights.sbomify.com/CVE-2024-8313/index.md)
```

## Sources

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

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