Kta1Kri

A denial of service vulnerability exists in the XML parsing of multiple versions of OpenNMS Meridian and Horizon. OpenNMS parsed XML without an effective limit on entity expansion. A document with a DOCTYPE that declares internal entities can expand to a very large value and exhaust the server memory. An authenticated user with provisioning access can supply such a document through a requisition or foreign-source import, which includes a remote requisition URL that the server fetches and parses. Both deeply nested entities and a single large entity referenced many times cause the memory exhaustion. The fix caps the number of entity expansions for all XML parsing and rejects any DOCTYPE in requisition and foreign-source XML. The solution is to upgrade to Meridian 2024.3.14, 2025.0.11, 2026.0.1 and Horizon 36.0.5 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.

**Name of the Vulnerable Software and Affected Versions** AAS edge client (affected versions not specified) **Description** An unauthenticated remote attacker can modify Asset Administration Shell submodel data through PATCH requests and read all exposed data via GET endpoints. This issue occurs via a REST API on port 18000, allowing unauthorized read and write access to industrial submodel data. **Recommendations** Decommission the AAS edge client.

**Name of the Vulnerable Software and Affected Versions** SiYuan versions prior to 3.8.4 **Description** Authentication guards `CheckAuth()` in `kernel/model/session.go` and `IsSessionOriginAllowed()` in `kernel/util/net.go` fail open when the HTTP Origin header is absent. This occurs because the system incorrectly assumes all browser-initiated cross-site requests include an Origin header. Since browsers omit this header during cross-site top-level GET navigations and no-cors GET subresource loads, and the session cookie uses SameSite=Lax, a cross-site GET request from an attacker-controlled page can be granted RoleAdministrator privileges. This affects both default installations and password-protected instances with active sessions. When combined with content-type sniffing on the '/api/network/proxy' endpoint, an unauthenticated remote attacker can serve malicious HTML under the SiYuan origin, execute arbitrary scripts, invoke administrator APIs, and exfiltrate the persistent kernel API token. **Recommendations** Update to version 3.8.4.

**Name of the Vulnerable Software and Affected Versions** GitPython versions prior to 3.1.62 **Description** GitPython fails to validate the `path` field read from an untrusted .gitmodules file during submodule updates. While constraints exist for the `name` field and certain operations like add and move, the `update()` function derives the absolute checkout location from the raw `path` value without proper guards. An attacker can use directory traversal components in the `path` field to cause the creation of directories outside the repository working tree via `os.makedirs()`, populate them from the submodule URL, or remove them using `shutil.rmtree()` when `force remove` is enabled. This issue is exploitable in application flows that update submodules at a non-HEAD commit, such as a historical-commit API. **Recommendations** Update GitPython to version 3.1.62.