CVE-2024-27455VulnerabilityPublished 26 Feb 2024Updated 14 Aug 2024

CVE-2024-27455: n/a

Source CVE Database V5

Not known to be exploited · CVSS 9.1 Critical · fixed in 23.00.04.04 : patch affected systems as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 23.00.04.04

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-27455, organizations should immediately upgrade to Assetwise ALIM Web version 23.00.04.04 and Assetwise Information Integrity Server version 23.00.02.03 or later, where the vulnerability is fixed. In addition to patching, administrators must review and harden configuration settings related to file downloads and session token handling to ensure tokens are never exposed in URLs, headers, or download responses. Implement strict access controls and session management policies, including token expiration and rotation, to minimize the window of opportunity for token reuse. Employ network-level protections such as web application firewalls (WAFs) configured to detect and block anomalous requests that might attempt to exploit token exposure. Enable comprehensive logging and monitoring to detect unusual access patterns or session anomalies indicative of token theft or session hijacking attempts. Educate users about the risks of session token exposure and encourage secure practices, such as logging out after sessions and avoiding use of shared or public networks when accessing ALIM Web. Finally, conduct regular security assessments and penetration testing focused on session management and data exposure vectors to proactively identify and remediate similar issues.

Description

In the Bentley ALIM Web application, certain configuration settings can cause exposure of a user's ALIM session token when the user attempts to download files. This is fixed in Assetwise ALIM Web 23.00.04.04 and Assetwise Information Integrity Server 23.00.02.03.

Impact

The impact of CVE-2024-27455 is substantial for organizations using Bentley ALIM Web applications, especially those managing critical infrastructure, engineering, and asset information. Successful exploitation allows attackers to hijack user sessions by capturing exposed session tokens, leading to unauthorized access to sensitive project data and internal systems. This compromises confidentiality and integrity, enabling data theft, unauthorized modifications, or disruption of workflows. Since no authentication or user interaction is required, the attack surface is broad and can be exploited remotely over the network. The vulnerability could facilitate lateral movement within enterprise environments if attackers leverage compromised sessions to escalate privileges or access additional resources. For organizations in sectors such as construction, utilities, transportation, and manufacturing that rely on Bentley's asset lifecycle information management, the breach could result in operational disruptions, intellectual property loss, regulatory non-compliance, and reputational damage. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the urgency for remediation given the critical severity and ease of exploitation.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-488Exposure of Data Element to Wrong Session (opens in a new tab)
Base weakness
The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
Architecture and Design
Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.
Testing
Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).
Architecture and Design
In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.
Attack patterns
Session Credential Falsification through Prediction (opens in a new tab)
Reusing Session IDs (aka Session Replay) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

bentley.com/advisories/be-2024-0001/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 22:26 UTC

WeaknessesCWE-613, CWE-488

Technical details

References

Community reviews

Related threats