Laura Pardo

**Name of the Vulnerable Software and Affected Versions** Ansible Lightspeed Model Context Protocol (MCP) server (affected versions not specified) **Description** A path traversal flaw exists in the Ansible Lightspeed Model Context Protocol (MCP) server. This issue allows an attacker to manipulate an AI agent via indirect prompt injection, which is a technique where malicious instructions are embedded in data that the AI processes. This manipulation can force the server to write files to unauthorized locations on the user's system, potentially exposing sensitive host information and allowing the execution of malicious commands, which could lead to a full system compromise. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

A flaw was found in the Ansible Lightspeed extension for Visual Studio Code. This vulnerability allows an attacker with local access to the workstation, or malware running with the user's privileges, to read the Google Gemini API key. The extension insecurely stores the API key in plain text within the user's configuration file and writes it to output log files. This information disclosure can lead to the attacker obtaining the API credential and potentially consuming the user's API quota.

A flaw was found in the Visual Studio Code Ansible Lightspeed extension's AnsiblePlaybookRunProvider. This command injection vulnerability allows an attacker to craft a malicious playbook filename containing special characters. When a victim runs the playbook, these characters are not properly sanitized, leading to the execution of arbitrary code with the privileges of the user running VS Code. This could result in a full system compromise, including the exfiltration of sensitive data, modification of project files, and permanent data loss.

A flaw was found in the Visual Studio Code Ansible Lightspeed extension. This command injection vulnerability (CWE-78) arises from improper handling of the ansible.executionEnvironment.containerOptions and ansible.executionEnvironment.volumeMounts settings, allowing an attacker to inject shell separators. This can be triggered automatically during Language Server initialization or manually when executing a playbook. Successful exploitation leads to remote code execution (RCE) on the victim's machine with the privileges of the Visual Studio Code user, potentially resulting in a complete system compromise.

**Name of the Vulnerable Software and Affected Versions** Ansible Lightspeed Visual Studio Code extension (affected versions not specified) **Description** A command injection flaw exists where the extension fails to properly validate user input as a file path within the `ansible.python.activationScript` setting. This setting is intended for virtual environment activation scripts. A remote attacker can exploit this by inducing a user to open or execute a specially crafted project, allowing the execution of unauthorized commands with the privileges of the Visual Studio Code application. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** foreman-mcp-server (affected versions not specified) Red Hat Satellite (affected versions not specified) **Description** A session management issue in the MCP Server allows unauthenticated attackers to hijack active administrative sessions. This occurs because the server improperly caches authenticated client connections, trusts non-secret session IDs without re-validating authentication tokens, and logs newly created session IDs to standard logs. Successful exploitation can lead to privilege escalation and infrastructure-wide code execution. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** foreman-mcp-server (affected versions not specified) **Description** Two distinct logging mechanisms in the software can expose sensitive session and authentication data. One mechanism logs session identifiers, which function as authentication credentials, at an informational level. A second mechanism, active when debug logging is enabled, fails to completely sanitize HTTP request headers, resulting in the cleartext logging of API keys and authorization tokens. This leads to a confidentiality breach where sensitive data is stored in plain text within container logs, which increases risk if logs are sent to a centralized platform. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Ansible Lightspeed (affected versions not specified) **Description** An issue exists due to insufficient session expiration, allowing a remote attacker to maintain persistent access to the instance. If a valid OAuth (Open Authorization) access token is exfiltrated before a user logs out, the attacker can continue to authenticate and access sensitive data. This occurs because the application does not invalidate the token on the backend, leaving it active until its natural expiration. This can result in unauthorized read access to resources such as inventories, playbooks, and configuration data. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Ansible Lightspeed (affected versions not specified) **Description** The Ansible Lightspeed API conversation endpoints, which manage AI chat interactions, do not adequately confirm if a conversation identifier corresponds to the authenticated user. This allows an attacker with valid credentials to access or modify conversations belonging to other users, potentially exposing sensitive data and enabling unauthorized manipulation of AI-generated outputs. The affected API endpoints are conversation endpoints. The vulnerable parameter is the conversation identifier. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** http-proxy-agent versions prior to 2.1.0 **Description** A flaw was found in http-proxy-agent where it passes an auth option to the Buffer constructor without proper sanitization. This could result in a Denial of Service through the usage of all available CPU resources and data exposure through an uninitialized memory leak in setups where an attacker could submit typed input to the `auth` parameter. **Recommendations** For versions prior to 2.1.0, update to version 2.1.0 or later to resolve the issue. As a temporary workaround, consider restricting the input to the `auth` parameter to prevent potential exploitation.

**Name of the Vulnerable Software and Affected Versions** Jolokia versions 1.2 through 1.6.0 **Description** A flaw in the software makes it vulnerable to a system-wide CSRF attack, even in properly configured instances with strict checking for origin and referrer headers. This could potentially result in a Remote Code Execution attack. **Recommendations** For Jolokia versions 1.2 through 1.6.0, update to version 1.6.1 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Keycloak versions prior to 6.0.2 **Description** A vulnerability was found in the X.509 authenticator, which supports the verification of client certificates through the Certificate Revocation List (CRL). The CRL can be obtained from the URL provided in the certificate itself (CDP) or through a separately configured path. However, the CRL is often available over the network through unsecured protocols, such as 'http' or 'ldap'. As a result, Keycloak's failure to validate signatures on CRL can lead to various attacks, including man-in-the-middle attacks. **Recommendations** For versions prior to 6.0.2, update to version 6.0.2 or later to resolve the issue. As a temporary workaround, consider restricting access to the X.509 authenticator or verifying the signature and certification path of the CRL manually until a patch is applied.

**Name of the Vulnerable Software and Affected Versions** WildFly versions 11 through 16 **Description** The issue is related to security checking implementation errors for standard elements in the Java application server. It may allow a remote attacker to impact the confidentiality and integrity of protected information. Specifically, the ElytronManagedThread in Wildfly's Elytron subsystem stores a SecurityIdentity to run the thread as, and these threads may not terminate even after the keep alive time has expired, potentially allowing a shared thread to use the wrong security identity when executing. **Recommendations** For WildFly versions 11 through 16, consider restricting access to the Elytron subsystem until a patch is available. As a temporary workaround, consider disabling the use of shared threads in the Elytron subsystem to minimize the risk of exploitation. Avoid using the ElytronManagedThread function in the affected Wildfly versions until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Red Hat Satellite versions prior to 6.2 Red Hat Satellite 6.1 optional Red Hat Satellite Capsule 6.1 **Description** A lack of access control was found in the message queues maintained by Satellite's QPID broker, which can be exploited by a malicious user authenticated to a host registered to Satellite or Capsule. This flaw allows access to QMF methods on any host registered to Satellite or Capsule, enabling the execution of privileged commands. **Recommendations** For Red Hat Satellite versions prior to 6.2, update to version 6.2 or later to resolve the issue. For Red Hat Satellite 6.1 optional, consider applying additional access controls to the QPID broker until an update to a fixed version is available. For Red Hat Satellite Capsule 6.1, restrict access to QMF methods until a patch or update is applied. As a temporary workaround, consider disabling access to the QPID broker's message queues for untrusted hosts until a fix is available.

**Name of the Vulnerable Software and Affected Versions** FreeRADIUS (affected versions not specified) **Description** The issue is related to insufficient authentication data validation in the FreeRADIUS server. It allows a remote attacker to gain unauthorized access to protected information. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** systemd-journald versions v221 through v239 **Description** An out of bounds read was discovered in the way systemd-journald parses log messages that terminate with a colon ':'. A local attacker can use this flaw to disclose process memory data. The issue is related to an error in handling messages that end with a colon, which may lead to the disclosure of memory data. **Recommendations** For versions v221 through v239, update to a version outside of this range to resolve the issue. As a temporary workaround, consider restricting access to the log parsing functionality until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Keycloak versions prior to 4.6.0.Final **Description** The issue concerns the SAML broker consumer endpoint in Keycloak, which ignores expiration conditions on SAML assertions. This can be exploited by an attacker to perform a replay attack. **Recommendations** For versions prior to 4.6.0.Final, update to version 4.6.0.Final or later to resolve the issue. As a temporary workaround, consider restricting access to the SAML broker consumer endpoint to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** JBOSS Keycloak version 3.2.1.Final **Description** A flaw was found in the software where the Redirect URL for both Login and Logout are not normalized in `org.keycloak.protocol.oidc.utils.RedirectUtils` before the redirect url is verified. This can lead to an Open Redirection attack. **Recommendations** For JBOSS Keycloak version 3.2.1.Final, consider disabling the `org.keycloak.protocol.oidc.utils.RedirectUtils` function until a patch is available to prevent potential Open Redirection attacks. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Keycloak versions 4.2.1.Final, 4.3.0.Final **Description** A flaw was found in the implementation of the Brute Force detection algorithm when TOPT is enabled, which will not enforce its protection measures. **Recommendations** For Keycloak version 4.2.1.Final, update to a version that fixes this issue. For Keycloak version 4.3.0.Final, update to a version that fixes this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Keycloak versions 3.4.3.Final through 4.3.0.Final **Description** A flaw in Keycloak allows the injection of arbitrary Javascript code via the `state`-parameter in the authentication URL when using `response mode=form post`. This enables a cross-site scripting (XSS) attack upon successful login. **Recommendations** For Keycloak versions 3.4.3.Final through 4.3.0.Final, consider disabling the use of `response mode=form post` until a patch is available to prevent the injection of arbitrary Javascript code via the `state`-parameter. Restrict access to the authentication URL to minimize the risk of exploitation. Avoid using the `state`-parameter in the affected authentication URL until the issue is resolved.