CVE-2023-52290

{"id": "CVE-2023-52290", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 2.8}]}, "published": "2024-07-16T08:15:02.050", "references": [{"url": "https://lists.apache.org/thread/t3mcm8pb65d9gj3wrgtj9sx9s2pfvvl3", "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2024/07/15/4", "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://lists.apache.org/thread/t3mcm8pb65d9gj3wrgtj9sx9s2pfvvl3", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-89"}]}], "descriptions": [{"lang": "en", "value": "In streampark-console the list pages(e.g: application pages), users can sort page by field. This sort field is sent from the front-end to the back-end, and the SQL query is generated using this field. However, because this sort field isn't validated, there is a risk of SQL injection vulnerability.\u00a0The attacker must successfully log into the system to launch an attack, which may cause data leakage. Since no data will be written, so this is a low-impact vulnerability.\n\nMitigation:\n\nall users should upgrade to 2.1.4, Such parameters will be blocked.\n\n"}, {"lang": "es", "value": "En streampark-console, las p\u00e1ginas de lista (por ejemplo, p\u00e1ginas de aplicaciones), los usuarios pueden ordenar las p\u00e1ginas por campo. Este campo de clasificaci\u00f3n se env\u00eda desde el front-end al back-end y la consulta SQL se genera utilizando este campo. Sin embargo, debido a que este campo de clasificaci\u00f3n no est\u00e1 validado, existe el riesgo de vulnerabilidad de inyecci\u00f3n SQL. El atacante debe iniciar sesi\u00f3n con \u00e9xito en el sistema para lanzar un ataque, lo que puede provocar una fuga de datos. Dado que no se escribir\u00e1n datos, esta es una vulnerabilidad de bajo impacto. Mitigaci\u00f3n: todos los usuarios deben actualizar a 2.1.4. Dichos par\u00e1metros se bloquear\u00e1n."}], "lastModified": "2024-11-21T08:39:31.530", "sourceIdentifier": "security@apache.org"}