| Título | Oinone Oinone Oinone <= 7.2.0 File Upload |
|---|
| Descripción | Oinone AI Low-Code Development Framework is a 100% metadata-driven framework. While most Oinone functions are controlled by the GraphQL permission gateway, LocalFileClient.java (a standard Spring RestController) is directly exposed at the /file/upload path, completely bypassing the system's intended permission validation logic.
The interface retrieves a filename via request.getParameter("uniqueFileName"). During the concatenation of the physical storage path, the system fails to filter or normalize directory traversal characters (e.g., ../). An attacker can construct a filename like ../../../../etc/cron.d/ and exploit the operating system's path resolution to escape the restricted storage directory. This allows them to write malicious instructions into the Linux system's scheduled tasks directory (cron.d) or overwrite any arbitrary file. |
|---|
| Fuente | ⚠️ https://github.com/SourByte05/SourByte-Lab/issues/14 |
|---|
| Usuario | sourbyte (UID 94279) |
|---|
| Sumisión | 2026-04-22 10:23 (hace 2 meses) |
|---|
| Moderación | 2026-05-16 12:30 (24 days later) |
|---|
| Estado | Aceptado |
|---|
| Entrada de VulDB | 364324 [Oinone Pamirs hasta 7.2.0 RestController LocalFileClient.java request.getParameter uniqueFileName recorrido de directorios] |
|---|
| Puntos | 20 |
|---|