dbcve.org
Assetwise Alim For TransportationApplication · Bentley

CVE-2023-51708

HIGH · 8.6 CVSS v3.1 Published 2023-12-22
Fix available
A fix is available. Upgrade to 23.00.01.25 / 23.00.02.03 or later.
See remediation →
95/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
Bentley eB System Management Console applications within Assetwise Integrity Information Server allow an unauthenticated user to view configuration options via a crafted request, leading to information disclosure. This affects eB System management Console before 23.00.02.03 and Assetwise ALIM For Transportation before 23.00.01.25.

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 an unauthenticated information disclosure vulnerability in Bentley eB System Management Console and Assetwise ALIM For Transportation. An attacker can send a crafted request to view sensitive configuration options without authentication, potentially exposing system settings, credentials, or other confidential data.

MitigationUpgrade eB System Management Console to version 23.00.02.03 or later, and Assetwise ALIM For Transportation to version 23.00.01.25 or later to obtain the patched software. If immediate patching is not possible, restrict network access to the management console interfaces via firewall rules or network segmentation.

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
Assetwise Alim For TransportationApplication
Affected:< 23.00.01.25
Eb System Management ConsoleApplication
Affected:< 23.00.02.03

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
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 Bentley eB System Management Console is installed
    Look for the application in the Windows Start Menu, Program Files directory, or check for the service named 'eB System Management Console' in Windows Services (services.msc). Also check for installation directories containing 'Bentley' or 'eB' in the name, typically under C:\Program Files\Bentley\ or C:\Program Files (x86)\Bentley\.
    Affected if The product is installed and the version is below 23.00.02.03
  2. Identify if Bentley Assetwise ALIM For Transportation is installed
    Look for the application in the Windows Start Menu, Program Files directory, or check for installation directories containing 'Assetwise' or 'ALIM' in the name. Check for processes named 'ALIM' or 'Assetwise' running on the system.
    Affected if The product is installed and the version is below 23.00.01.25
  3. Determine the installed version of eB System Management Console
    Open Windows Services (services.msc), locate the eB System Management Console service, right-click and select Properties. The version may be shown in the 'Path to executable' or check the executable's properties by navigating to that file. Alternatively, right-click the application in Start Menu and select 'Open file location' to find the executable, then right-click the .exe file, select Properties, and check the Details tab for version information.
    Affected if The displayed version is below 23.00.02.03 or version information cannot be determined and the product is installed
  4. Determine the installed version of Assetwise ALIM For Transportation
    Open Windows Services (services.msc), locate any Assetwise or ALIM-related service, right-click and select Properties. The version may be shown in the 'Path to executable' or check the executable's properties. Alternatively, check the installation directory for a version file or check the application's About/Help section.
    Affected if The displayed version is below 23.00.01.25 or version information cannot be determined and the product is installed
  5. Check if management console interfaces are network-accessible
    Review firewall rules and network configuration to determine if the management console ports (typically port 8080, 8443, or custom ports configured during installation) are exposed to untrusted networks. Use 'netstat -an' or review inbound firewall rules to identify listening ports associated with these applications.
    Affected if Management console interfaces are listening on ports accessible from untrusted networks (such as the internet or non-segmented internal networks)

A user is affected if either Bentley eB System Management Console below version 23.00.02.03 or Bentley Assetwise ALIM For Transportation below version 23.00.01.25 is installed AND the management console interface is network-accessible to untrusted users.

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
Upgrade available Upgrade to 23.00.01.25 / 23.00.02.03 or later
Fixed in 23.00.01.2523.00.02.03
Interim mitigation

Upgrade eB System Management Console to version 23.00.02.03 or later, and Assetwise ALIM For Transportation to version 23.00.01.25 or later to obtain the patched software. If immediate patching is not possible, restrict network access to the management console interfaces via firewall rules or network segmentation.

Recommended fix High confidence

Assetwise ALIM For Transportation: 23.00.01.25 or later | eB System Management Console: 23.00.02.03 or later

  1. 1. Identify which product is deployed: Assetwise ALIM For Transportation or eB System Management Console
  2. 2. Check current installed version to confirm it is vulnerable (< 23.00.01.25 for Assetwise ALIM or < 23.00.02.03 for eB System Management Console)
  3. 3. Create a full backup of the current configuration and database
  4. 4. Obtain the updated installer from Bentley's official distribution channel
  5. 5. Upgrade Assetwise ALIM For Transportation to version 23.00.01.25 or later, OR upgrade eB System Management Console to version 23.00.02.03 or later
  6. 6. Apply any post-upgrade migration scripts if provided
  7. 7. Restart all related services
  8. 8. Verify the upgrade was successful by checking the version number

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

Fix this in Assetwise Alim For Transportation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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