dbcve.org
Industrial Automation AprolApplication · Br Automation

CVE-2024-5622

HIGH · 7.8 CVSS v3.1 Published 2024-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 untrusted search path vulnerability in the AprolConfigureCCServices of B&R APROL <= R 4.2.-07P3 and <= R 4.4-00P3 may allow an authenticated local attacker to execute arbitrary code with elevated privileges.

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

An untrusted search path vulnerability in the AprolConfigureCCServices component of B&R APROL allows an authenticated local attacker to execute arbitrary code with elevated privileges by placing malicious executables in a directory that precedes the legitimate location in the application's search path.

MitigationApply vendor patches for APROL R 4.2-07P3 and R 4.4-00P3; until patched, restrict write access to directories in the application search path and monitor for unauthorized binary placement.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Industrial Automation AprolApplication
Affected:<= r4.2-07p3>= r4.3-00p3, <= r4.4-00p3

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 APROL installation and version
    Locate the APROL installation directory and check for version information files. Common locations include /opt/aprol or C:\Program Files\B&R Automation. Look for version.txt, version.info, or check the About dialog in APROL configuration tools.
    Affected if The installed version is <= r4.2-07p3 OR (>= r4.3-00p3 AND <= r4.4-00p3)
  2. Verify AprolConfigureCCServices component presence
    Search for the AprolConfigureCCServices executable or service in the APROL installation. Check the bin or services subdirectory for AprolConfigureCCServices.exe or similar binaries.
    Affected if The AprolConfigureCCServices component is installed on the system
  3. Examine application search path configuration
    Review PATH environment variable and any application-specific path configurations. Use 'echo %PATH%' on Windows or 'echo $PATH' on Linux. Check APROL configuration files for custom path settings.
    Affected if Directories with weak permissions appear before legitimate APROL binary directories in the search path
  4. Inspect directories in search path for unauthorized binaries
    List contents of each directory in the application search path, focusing on directories writable by non-admin users. Look for unexpected executables, especially in directories that appear earlier in the PATH than the legitimate APROL bin directory.
    Affected if Unexpected executables are found in directories that precede the legitimate APROL binaries in the search path
  5. Review write permissions on search path directories
    Use OS-native commands to check ACLs. On Windows: icacls or PowerShell Get-Acl. On Linux: ls -la or namei -l. Identify directories writable by standard users or groups.
    Affected if Any directory in the APROL search path is writable by unprivileged users

The system is affected if APROL version is within r4.2-07p3 and below, or between r4.3-00p3 and r4.4-00p3 inclusive, AND the AprolConfigureCCServices component is installed, AND writable directories exist in the search path before legitimate binary locations.

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 patches for APROL R 4.2-07P3 and R 4.4-00P3; until patched, restrict write access to directories in the application search path and monitor for unauthorized binary placement.

Recommended fix Moderate confidence

B&R APROL r4.2-07p4 or later / r4.4-00p4 or later (contact vendor for exact fixed release)

  1. 1. Contact B&R Automation support directly to obtain the specific patched version for your APROL release (r4.2 or r4.4)
  2. 2. Request the security patch for CVE-2024-5622 addressing the untrusted search path in AprolConfigureCCServices
  3. 3. Before applying the patch, back up all Aprol configuration files and project data
  4. 4. Apply the vendor-provided patch in a test environment first
  5. 5. Validate that AprolConfigureCCServices functions correctly with the patch applied
  6. 6. Deploy the patched version to production during a scheduled maintenance window
Caveat Review vendor release notes for any configuration changes required for AprolConfigureCCServices after patching

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

Fix this in Industrial Automation Aprol Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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