Nebula

Cross site scripting occurs in the DHCP Hostname Handler component due to the improper handling of the `Hostname` argument within the `eval()` function of the 'filter hosts dump.cgi' endpoint. This allows for remote exploitation.

Cross site scripting occurs in the Web UI component due to improper handling of the `title`, `note`, `URL`, and `content` arguments within the `eval()` function of the '/router/l7 call board user set.cgi' endpoint. This allows a remote attacker to execute malicious scripts.

A security flaw has been discovered in Netcore NR268 1.7.121109. Affected by this issue is some unknown functionality of the component CGI Endpoint. Performing a manipulation results in cross-site request forgery. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

An argument injection flaw exists in the DDNS component. A remote attacker can exploit this by manipulating the `Hostname` argument passed to the `execvp()` function within the '/router/DDNSset.cgi' endpoint.

An issue exists in the DDNS Handler component within the `ddns wan list show()` function of the `ddns wan list show.cgi` file. Remote manipulation of the `user idN` and `passwordN` arguments can lead to information disclosure.

Cross site scripting occurs in the DHCP Handler component when the `eval()` function in the `dhcp dynamicip show.cgi` file improperly handles the `Hostname` argument. This allows a remote attacker to execute malicious scripts.

A vulnerability has been found in Netcore NR268 1.7.121109. This affects the function filter arp put file cgi of the file /router/filter arp put file.cgi. The manipulation of the argument put file leads to out-of-bounds read. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Improper authentication exists in the CGI Execution component. A remote attacker can manipulate the `user ok()` function to bypass authentication mechanisms.

Name of the Vulnerable Software and Affected Versions: Spring Framework versions 3.0.0 through 3.2.8 Spring Framework versions 4.0.0 through 4.0.4 Description: The issue arises when processing user-provided XML documents, as the Spring Framework did not disable by default the resolution of URI references in a DTD declaration, enabling an XXE attack. Recommendations: For Spring Framework versions 3.0.0 through 3.2.8, disable the resolution of URI references in DTD declarations to prevent XXE attacks. For Spring Framework versions 4.0.0 through 4.0.4, disable the resolution of URI references in DTD declarations to prevent XXE attacks.

The issue is related to the ParametersInterceptor in Apache Struts, which does not properly restrict access to the getClass method. This allows remote attackers to manipulate the ClassLoader and execute arbitrary code via a crafted request. The vulnerability exists due to an incomplete fix for a previous issue. It is related to the implementation of the getClass method, which has access control deficiencies when using the ParametersInterceptor with the class parameter. Exploitation of this vulnerability can allow a remote attacker to execute arbitrary code by sending a specially crafted request.

The issue is related to the CookieInterceptor in Apache Struts, where an incomplete fix for a previous issue has led to a vulnerability. This vulnerability allows remote attackers to manipulate the ClassLoader and execute arbitrary code via a crafted request, due to insufficient access restrictions when handling wildcard cookiesName values. The exploitation requires the application to be configured to accept all cookies, allowing access to the class parameter directly mapped to the getClass() method.

The issue allows remote attackers to inject arbitrary web script or HTML via the `namespace` parameter to specific API endpoints, including "actionNames.action" and "showConfig.action" in the `config-browser/` directory. This enables attackers to execute malicious scripts on the victim's browser.