CVE-2024-1681

{"id": "CVE-2024-1681", "metrics": {"cvssMetricV30": [{"type": "Secondary", "source": "security@huntr.dev", "cvssData": {"scope": "UNCHANGED", "version": "3.0", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "published": "2024-04-19T20:15:09.273", "references": [{"url": "https://huntr.com/bounties/25a7a0ba-9fa2-4777-acb6-03e5539bb644", "source": "security@huntr.dev"}, {"url": "https://huntr.com/bounties/25a7a0ba-9fa2-4777-acb6-03e5539bb644", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security@huntr.dev", "description": [{"lang": "en", "value": "CWE-117"}]}], "descriptions": [{"lang": "en", "value": "corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tracks of other attacks, confusing log post-processing tools, and forging log entries. The issue is due to improper output neutralization for logs."}, {"lang": "es", "value": "corydolphin/flask-cors es vulnerable a la inyecci\u00f3n de registros cuando el nivel de registro est\u00e1 configurado para depurar. Un atacante puede inyectar entradas de registro falsas en el archivo de registro enviando una solicitud GET especialmente manipulada que contenga una secuencia CRLF en la ruta de la solicitud. Esta vulnerabilidad permite a los atacantes corromper archivos de registro, cubriendo potencialmente pistas de otros ataques, confundiendo las herramientas de posprocesamiento de registros y falsificando entradas de registro. El problema se debe a una neutralizaci\u00f3n inadecuada de la salida de los registros."}], "lastModified": "2024-11-21T08:51:04.453", "sourceIdentifier": "security@huntr.dev"}