dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-45480

CRITICAL · 9.2 CVSS v4.0 Published 2025-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper control of generation of code ('Code Injection') vulnerability in the AprolCreateReport component of B&R APROL <4.4-00P5 may allow an unauthenticated network-based attacker to read files from the local system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Code Injection vulnerability exists in the AprolCreateReport component of B&R APROL versions prior to 4.4-00P5. An unauthenticated network attacker can exploit this flaw to read arbitrary files from the local system, potentially exposing sensitive configuration data, credentials, or other confidential information.

MitigationUpgrade B&R APROL to version 4.4-00P5 or later. If immediate patching is not possible, restrict network access to the affected system and implement additional network segmentation to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if B&R APROL is installed
    Check system for B&R APROL software installation. On Windows, review installed programs in Control Panel > Programs and Features. On industrial systems, check common installation directories such as C:\BrAutomation or C:\Program Files\B&R Automation.
    Affected if B&R APROL software is found on the system
  2. Determine the installed APROL version
    Locate the version information for the APROL installation. Check the About section in the APROL configuration interface, review version files in the installation directory, or use system information tools to identify the build version.
    Affected if The installed version is identified as lower than 4.4-00P5 (for example, 4.4-00P4, 4.3-x, or earlier versions)
  3. Verify AprolCreateReport component presence
    Identify if the AprolCreateReport component is installed and available. Review the APROL component list or configuration to determine if this reporting module is part of the deployment.
    Affected if AprolCreateReport component is installed and active in the APROL system
  4. Check network accessibility of the vulnerable service
    Determine if the APROL web services or reporting interfaces are exposed to the network. Review firewall rules, network configuration, and listening services on the system to identify accessible ports related to APROL.
    Affected if APROL services are reachable from the network (especially untrusted networks)

A system is affected if B&R APROL with version prior to 4.4-00P5 is installed, the AprolCreateReport component is present, and the service is network-accessible to unauthenticated attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade B&R APROL to version 4.4-00P5 or later. If immediate patching is not possible, restrict network access to the affected system and implement additional network segmentation to limit exposure.

Recommended fix Moderate confidence

B&R APROL 4.4-00P5 or later

  1. Upgrade B&R APROL to version 4.4-00P5 or later to remediate the Code Injection vulnerability in the AprolCreateReport component.
  2. After upgrading, verify that the AprolCreateReport component functions correctly and that file access is properly restricted.
  3. Review system logs for any signs of exploitation attempts targeting this vulnerability prior to patching.
  4. If upgrading is not immediately possible, network-segment the affected system and restrict access to the AprolCreateReport component from untrusted networks.
Caveat Review B&R release notes for 4.4-00P5 to confirm no breaking changes affect your specific APROL configuration and customizations.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45480 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data