gin-vue-admin Hintergrund beliebige Code Coverage Schwachstelle

The impact of this vulnerability is significant. By manipulating the plugName parameter, an attacker can bypass directory traversal restrictions and create arbitrary files within the system. This allows them to inject malicious code, such as Go files, into critical directories like api, config, global, model, router, and service. The ability to create and execute arbitrary code within these directories could grant the attacker complete control over the backend system, potentially leading to data breaches, system compromise, and denial of service. The full-stack nature of gin-vue-admin means that a successful attack could impact both the backend and frontend components, expanding the potential blast radius.

Organizations using gin-vue-admin for their backend management systems are at risk, particularly those running older, unpatched versions. Shared hosting environments where multiple users have access to the plugin management features are especially vulnerable, as a compromised plugin could affect the entire hosting instance. Any deployment relying on the default plugin template functionality without proper input validation is also at increased risk.

• linux / server:

find /opt/gin-vue-admin/plugins/ -name '*api*.go' -o -name '*config*.go' -o -name '*global*.go' -o -name '*model*.go' -o -name '*router*.go' -o -name '*service*.go' -o -name '*main.go*' 2>/dev/null

• generic web:

curl -I 'http://your-gin-vue-admin-instance/plugins/api/some..directory.go' # Check for 403 or other error indicating traversal is blocked

1. 2024-04-09Disclosure

   disclosure

2. 2024-04-09Patch

   patch

1. Reserviert2024-04-03
2. Veröffentlicht2024-04-09
3. Geändert2024-08-02
4. EPSS aktualisiert2026-04-02

The primary mitigation for CVE-2024-31457 is to immediately upgrade to version 0.0.0-20240409100909-b1b7427c6ea6 or later. If upgrading is not immediately feasible, consider implementing temporary workarounds. Restrict access to the Plugin System -> Plugin Template feature to trusted users only. Implement strict input validation on the plugName parameter, ensuring it only accepts alphanumeric characters and prevents directory traversal sequences (e.g., ../). Web application firewalls (WAFs) can be configured to block requests containing suspicious directory traversal patterns. Monitor system logs for unusual file creation activity within the plugin directories. After upgrading, confirm the fix by attempting to create a file using a directory traversal payload in the plugName parameter; the request should be rejected.