Alessandro Bosco

An issue exists in the Network Element Manager, specifically a Reflected XSS. This issue can be exploited via several API endpoints, including "/oms1350/pages/otn/cpbLogDisplay" via the `filename` parameter, under "/oms1350/pages/otn/connection/E2ERoutingDisplayWithOverLay" via the `id` parameter, and under "/oms1350/pages/otn/mainOtn" via all parameters.

A SQL Injection issue occurs in the /cgi-bin/R19.9/easy1350.pl endpoint of the VM Manager WebUI, specifically via the `id` or `host` HTTP GET parameters. This issue requires an authenticated attacker for exploitation.

An Unprotected Storage of Credentials issue occurs in the Network Element Manager under `/root/RestUploadManager.xml.DRC` and `/DEPOT/KECustom 199/OTNE DRC/RestUploadManager.xml`. A remote user, authenticated to the operating system with access privileges to the directory `/root` or `/DEPOT`, can read cleartext credentials to access the web portal NFM-T and control all the PPS Network elements.

The issue allows relative path traversal via a specific parameter in the https request after authentication, which enables access to files on the system that are not intended to be accessible via the web application.

The issue allows users belonging to the same AMOS authorization group to retrieve data from certain log files, potentially leading to privilege escalation. All AMOS users are considered highly privileged in the ENM system and must be previously defined and authorized by the Security Administrator. These users can access log files under a common path and read stored information to conduct privilege escalation.

Under certain circumstances, an unauthenticated user could access the web API and enumerate users.

The issue allows unauthenticated remote attackers to inject arbitrary web script or HTML into an HTTP GET parameter that reflects user input without sanitization. This exists on numerous application endpoints.

The issue is related to OS Command Injection, where the software does not properly check the parameters sent as input before they are processed on the server. Due to the lack of validation of user input, an unauthenticated attacker can bypass the syntax intended by the software and inject arbitrary system commands with the privileges of the application user. This can be achieved by concatenating commands, such as `&|;r` commands.

The issue is related to Improper Access Control in authorization logic, allowing an unauthenticated user to access some critical resources.

The issue concerns incorrect access-control behavior, affecting users with highly privileged roles. It allows users within the same AMOS authorization group to retrieve managed-network data not intended for their access, specifically data restricted to a subset of the group.

Name of the Vulnerable Software and Affected Versions: Thruk versions prior to 2.44 Description: The issue allows for stored XSS, potentially enabling attackers to inject malicious scripts into the application. This could lead to unauthorized access or control of user sessions. Recommendations: For versions prior to 2.44, update to version 2.44 or later to resolve the issue. As a temporary workaround, consider restricting access to sensitive features or input fields to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Thruk versions 2.40-2 Description: The issue allows for Reflected XSS via the `host` or `service` parameter in the `/thruk/#cgi-bin/extinfo.cgi` API endpoint. An attacker could inject arbitrary JavaScript into extinfo.cgi, and the malicious payload would be triggered every time an authenticated user browses the page containing it. Recommendations: For Thruk versions 2.40-2, consider disabling access to the `/thruk/#cgi-bin/extinfo.cgi` API endpoint until a patch is available. Restrict the use of the `host` and `service` parameters to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Thruk versions 2.40 through 2 Description: The issue allows for Reflected XSS via the `host` or `title` parameter in the "/thruk/#cgi-bin/status.cgi" endpoint. An attacker could inject arbitrary JavaScript into status.cgi, which would be triggered every time an authenticated user browses the page containing it. Recommendations: For Thruk versions 2.40 through 2, as a temporary workaround, consider restricting access to the "/thruk/#cgi-bin/status.cgi" endpoint until a patch is available. Avoid using the `host` or `title` parameters in this endpoint to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this issue.

The issue affects OSS-RC systems during data migration procedures, where files containing `usernames` and `passwords` are left undeleted in folders accessible by top privileged accounts only. This issue only affects products that are no longer supported by the maintainer. It is recommended that OSS-RC customers upgrade to Ericsson Network Manager, a new generation OSS system.

The issue affects customer documentation browsing libraries under ALEX in OSS-RC systems, making them subject to Cross-Site Scripting. This problem is resolved in the new Ericsson library browsing tool ELEX used in systems like Ericsson Network Manager. The vulnerability only affects products that are no longer supported by the maintainer.

The issue is related to inadequate access control in the BI Platform Security component of Oracle Business Intelligence Enterprise Edition. This easily exploitable vulnerability allows an unauthenticated attacker with network access via HTTP to compromise the system. Successful attacks require human interaction from a person other than the attacker and may significantly impact additional products. The vulnerability can result in unauthorized read access to a subset of Oracle Business Intelligence Enterprise Edition accessible data.

The issue is related to insufficient input validation in the Analytics Actions component of Oracle Business Intelligence Enterprise Edition. This can be exploited by a remote attacker to gain unauthorized access to protected information or cause a partial denial of service using the HTTP protocol. Successful attacks may require human interaction and can impact additional products, resulting in unauthorized access to data and potential partial denial of service.

The issue is related to insufficient input validation in the BI Publisher Security component. It allows an unauthenticated attacker with network access via HTTP to compromise BI Publisher, potentially leading to unauthorized access to critical data or complete access to all BI Publisher accessible data. Successful attacks may also result in unauthorized update, insert, or delete access to some of BI Publisher's accessible data. The attack requires human interaction from a person other than the attacker and can significantly impact additional products.

The issue is related to insufficient access control in the Analytics Actions component of Oracle Business Intelligence Enterprise Edition. This can be exploited by a remote attacker to gain read, modify, add, or delete access to data using the HTTP protocol. Successful attacks may require human interaction and can significantly impact additional products, resulting in unauthorized access to critical data or complete access to all accessible data, as well as unauthorized update, insert, or delete access to some accessible data.