dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-45484

HIGH · 7.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 →
77/100
Remediation priority · High
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 Allocation of Resources Without Limits or Throttling vulnerability in the operating system network configuration used in B&R APROL <4.4-00P5 may allow an unauthenticated adjacent attacker to per-form Denial-of-Service (DoS) attacks against the product.

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 · moderate confidence

B&R APROL versions prior to 4.4-00P5 contain an allocation of resources without limits or throttling vulnerability in the operating system network configuration. An unauthenticated adjacent attacker can exploit this flaw to consume excessive system resources, resulting in denial of service against the industrial control product.

MitigationUpgrade B&R APROL to version 4.4-00P5 or later. Until upgrade is possible, implement network segmentation and access controls to restrict adjacent network attackers from reaching the APROL system.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/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 for APROL installation directories, services, or installed programs on the system. Common locations may include C:\Program Files\BR\APROL or /opt/aprol. Look for APROL-related services running on the host.
    Affected if B&R APROL software is found on the system
  2. Determine installed APROL version
    Locate the APROL version information, typically found in the product's about dialog, installation logs, or version file within the APROL installation directory. Common file names include version.txt, about.html, or the main executable's properties.
    Affected if Version cannot be determined or is prior to 4.4-00P5
  3. Compare version against affected range
    Verify the installed version number against the vulnerable range: versions prior to 4.4-00P5 are affected. If version starts with 4.4, ensure it is 4.4-00P5 or later (e.g., 4.4-00P5, 4.4-01, etc.).
    Affected if Installed version is 4.4-00P4 or earlier, or any version starting with 4.3, 4.2, etc.
  4. Assess network accessibility
    Determine if the APROL system is reachable from adjacent network segments. Check firewall rules, network segmentation, and interface bindings to identify if the APROL management or network configuration interfaces are exposed beyond the local subnet.
    Affected if APROL network services are accessible from network segments beyond the trusted local network without proper access controls

The system is affected if B&R APROL is installed with a version prior to 4.4-00P5 and the network configuration interfaces are accessible from adjacent network segments.

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. Until upgrade is possible, implement network segmentation and access controls to restrict adjacent network attackers from reaching the APROL system.

Recommended fix Moderate confidence

4.4-00P5 or later

  1. Identify the current B&R APROL version installed in the system
  2. Contact B&R Automation (www.br-automation.com) to obtain the upgrade package for version 4.4-00P5 or later
  3. Follow B&R's documented upgrade procedure to update the APROL system to version 4.4-00P5 or newer
  4. After upgrade, verify the network configuration vulnerability has been addressed

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45484 — 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-45484 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