Description

A vulnerability has been found in NocteDefensor LudusMCP 1.0.24. Affected by this vulnerability is an unknown functionality of the file src/tools/rangeConfig.ts of the component read_range_config. The manipulation of the argument Source leads to server-side request forgery. The attack may be initiated remotely. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-09T20:16:40.007Z",
  "pubdate": "2026-08-09T20:16:40.007Z",
  "executiveSummary": "A Server-Side Request Forgery vulnerability has been identified in NocteDefensor LudusMCP version 1.0.24. The flaw resides within the read_range_config component, specifically inside the src/tools/rangeConfig.ts file. This security defect arises from improper handling of user-supplied input passed via the Source argument, allowing an unauthenticated remote attacker to induce the server into executing arbitrary outbound requests.\nThe primary impact of this vulnerability involves the potential exposure of internal network resources, sensitive metadata services, and backend systems that are normally inaccessible from the external perimeter. By manipulating the Source parameter, threat actors can leverage the hosting server as a proxy to scan internal ports, interact with local loopback services, or exfiltrate confidential data.\nThe vulnerability represents a significant risk to confidentiality and internal network integrity, particularly given that the attack vector is exposed remotely without requiring prior authentication or privileged access. Remediation is complicated by the lack of an official vendor response following early disclosure through an issue report.",
  "technicalDetails": "The vulnerability is classified as Server-Side Request Forgery and stems from insufficient validation and sanitization of input parameters processed by the read_range_config component in NocteDefensor LudusMCP version 1.0.24. Specifically, the source code file src/tools/rangeConfig.ts accepts an externally controllable argument designated as Source, which dictates the target endpoint for data retrieval or configuration reading operations.\nRoot Cause Analysis: The underlying defect is the direct utilization of unvalidated user input within backend network request execution functions. When the application processes the Source argument, it fails to enforce strict URL parsing, scheme whitelisting, or IP address filtering. Consequently, the application interprets the supplied string and initiates an outbound connection without restricting destinations to authorized external domains or safely bounded resources.\nAttack Vector and Flow: An unauthenticated remote attacker initiates the exploitation phase by crafting a malicious HTTP request or protocol-specific payload targeting the LudusMCP instance. Within this payload, the attacker modifies the Source argument to point toward internal assets, such as private IP ranges (e.g., 127.0.0.1, 10.0.0.0/8, 192.168.0.0/16), cloud provider metadata endpoints (e.g., 169.254.169.254), or unauthorized external servers. Upon receiving the input, the src/tools/rangeConfig.ts logic processes the value and executes the request using the server's network stack and privileges.\nPost-Exploitation Impact: Successful exploitation enables the attacker to bypass perimeter firewalls and network segmentation controls. Depending on the internal network architecture, the attacker may retrieve sensitive configuration files, interact with unprotected internal APIs, execute internal port scanning, or consume internal services that trust local originations. The lack of authentication and privilege requirements maximizes the severity of the attack surface exposed by the read_range_config component."
}