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

CVE-2024-10206

MEDIUM · 6.9 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 →
78/100
Remediation priority · High
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
A Server-Side Request Forgery vulnerability in the APROL Web Portal used in B&R APROL <4.4-00P5 may allow an unauthenticated 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 · high confidence

Server-Side Request Forgery (SSRF) in B&R APROL Web Portal versions prior to 4.4-00P5 allows an unauthenticated remote attacker to induce the web server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services, enabling port scanning of internal networks, or bypassing firewall restrictions.

MitigationApply vendor patch 4.4-00P5 or later to address the SSRF vulnerability; if immediate patching is not feasible, implement network segmentation to restrict the web server's outbound connectivity and monitor for suspicious inbound requests to internal resources.

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: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 B&R APROL Web Portal installation
    Locate the APROL installation directory or check system services for 'APROL' or 'WebPortal' processes. On Windows, check Program Files for B&R folders; on Linux, check /opt or common application directories.
    Affected if The B&R APROL Web Portal software is installed on the system
  2. Determine installed APROL version
    Check the About or Version information within the APROL Web Portal interface, or inspect version files in the installation directory. Typical locations include a 'version.txt', 'info' file, or the application's help/about dialog.
    Affected if The installed version is any version prior to 4.4-00P5 (e.g., 4.4-00, 4.3-x, 4.2-x, or earlier)
  3. Verify web portal is network accessible
    Confirm the APROL Web Portal HTTP/HTTPS service is listening on its configured port (typically port 80/443 or a custom port). Use 'netstat -an | grep <port>' or check if the web interface responds to requests.
    Affected if The web portal is exposed to network traffic and responds to HTTP requests
  4. Check for unauthenticated access to web portal
    Attempt to access the web portal login page or main interface without credentials. Determine if the SSRF-vulnerable endpoint is reachable without authentication.
    Affected if The web portal or specific endpoints are accessible without authentication

A system is affected if it has B&R APROL Web Portal installed with a version prior to 4.4-00P5 and the web interface is network-accessible.

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

Apply vendor patch 4.4-00P5 or later to address the SSRF vulnerability; if immediate patching is not feasible, implement network segmentation to restrict the web server's outbound connectivity and monitor for suspicious inbound requests to internal resources.

Recommended fix High confidence

B&R APROL 4.4-00P5 or later

  1. Identify the current B&R APROL version running in your environment
  2. Plan the upgrade to version 4.4-00P5 or later, reviewing the vendor release notes for any compatibility or configuration changes
  3. Create a full backup of the APROL system and configuration data
  4. Upgrade the B&R APROL system to version 4.4-00P5 or the latest available stable release following the vendor's official upgrade documentation
  5. After upgrading, verify that the APROL Web Portal is functioning correctly and that the SSRF vulnerability is no longer present
  6. Confirm the installed version matches or exceeds 4.4-00P5
Caveat Review B&R release notes for any compatibility changes or configuration adjustments required when upgrading to 4.4-00P5

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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