CyberRota Analysis
AI-GeneratedEclipse BaSyx AAS Web UI versions prior to v2-260924 are vulnerable due to a flaw in the shared request handler, which improperly attaches the `Authorization` header to outgoing requests without validating the destination origin. This allows an attacker to craft a malicious link that, when opened by a user, can lead to the disclosure of sensitive authentication credentials, enabling unauthorized access to protected AAS services. Organizations using affected versions, particularly those with authentication mechanisms in place, should prioritize this vulnerability to mitigate potential credential theft and unauthorized access.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
In Eclipse BaSyx AAS Web UI versions v2-241220 through releases before v2-260924, the shared request handler attached the selected infrastructure's `Authorization` header to outgoing requests without checking the destination origin. In deployments using authentication, an attacker could induce a user to open a crafted Web UI link whose `aas` or `path` query parameter points to an attacker-controlled endpoint. The user's browser would then send the configured Basic Authentication credentials, Bearer token, or an available OAuth2 access token to that endpoint. The attacker could reuse the disclosed credential to access protected AAS services with the victim's privileges. The issue is fixed in v2-260924.