dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-10207

MEDIUM · 5.3 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 →
59/100
Remediation priority · Elevated
Remotely reachable 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
A Server-Side Request Forgery vulnerability in the APROL Web Portal used in B&R APROL <4.4-00P5 may allow an authenticated network-based attacker to force the web server to request arbitrary URLs.

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

This is a Server-Side Request Forgery (SSRF) vulnerability in the APROL Web Portal component of B&R APROL versions prior to 4.4-00P5. An authenticated network-based attacker can exploit this flaw to force the web server to make requests to arbitrary URLs, potentially enabling internal service enumeration, access to protected internal resources, or bypassing network segmentation.

MitigationUpgrade B&R APROL to version 4.4-00P5 or later. Additionally, implement network segmentation and restrict outbound access from the APROL server to minimize the impact of potential SSRF exploitation.

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/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 processes running on the system (such as 'APROL' or 'br.aprol' processes) or look for APROL installation directories on the system.
    Affected if APROL software is present and running on the system
  2. Determine the installed APROL version
    Locate the APROL version information, typically found in the system configuration, about dialog, or installation directory (commonly in program files or system-specific paths).
    Affected if The version is lower than 4.4-00P5 (for example, 4.4-00, 4.3-x, or earlier)
  3. Verify the APROL Web Portal component is enabled
    Check if the web portal service or module is running and accessible. This may be indicated by listening ports (typically 443, 8443, or custom HTTP/HTTPS ports) associated with APROL web services.
    Affected if The APROL Web Portal is enabled and accessible on the network
  4. Confirm web portal authentication configuration
    Review the APROL web portal authentication settings to determine if authentication is required for access. SSRF in this case requires an authenticated attacker.
    Affected if The web portal is accessible without proper authentication or uses default/weak credentials
  5. Check network exposure of the web portal
    Identify which network interfaces and IP addresses the APROL web portal is bound to. Determine if it listens on all interfaces (0.0.0.0) or is restricted to specific internal networks.
    Affected if The web portal is exposed to untrusted networks or directly accessible from the internet

You are affected if B&R APROL with a version prior to 4.4-00P5 is installed and the APROL Web Portal component is enabled and accessible, regardless of authentication status since an authenticated attacker can exploit the SSRF.

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. Additionally, implement network segmentation and restrict outbound access from the APROL server to minimize the impact of potential SSRF exploitation.

Recommended fix Moderate confidence

4.4-00P5 or later

  1. 1. Identify the current B&R APROL version by checking the system information or contacting B&R support
  2. 2. Download APROL version 4.4-00P5 or later from the B&R automation website or contact B&R technical support
  3. 3. Review B&R's upgrade documentation and release notes for version 4.4-00P5
  4. 4. Perform the upgrade following B&R's recommended upgrade procedure
  5. 5. After upgrade, verify the SSRF vulnerability is resolved by confirming the fixed version is installed

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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