CVE-2025-46653

{"id": "CVE-2025-46653", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "cve@mitre.org", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.1, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.6}]}, "published": "2025-04-26T21:15:14.403", "references": [{"url": "https://github.com/node-formidable/formidable/blob/d0fbec13edc8add54a1afb9ce1a8d3db803f8d47/CHANGELOG.md?plain=1#L10", "source": "cve@mitre.org"}, {"url": "https://github.com/node-formidable/formidable/commit/022c2c5577dfe14d2947f10909d81b03b6070bf5", "source": "cve@mitre.org"}, {"url": "https://github.com/zast-ai/vulnerability-reports/blob/main/formidable/file_upload/report.md", "source": "cve@mitre.org"}, {"url": "https://github.com/zast-ai/vulnerability-reports/blob/main/formidable/file_upload/report.md", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "cve@mitre.org", "description": [{"lang": "en", "value": "CWE-338"}]}], "descriptions": [{"lang": "en", "value": "Formidable (aka node-formidable) 2.1.0 through 3.x before 3.5.3 relies on hexoid to prevent guessing of filenames for untrusted executable content; however, hexoid is documented as not \"cryptographically secure.\" (Also, there is a scenario in which only the last two characters of a hexoid string need to be guessed, but this is not often relevant.) NOTE: this does not imply that, in a typical use case, attackers will be able to exploit any hexoid behavior to upload and execute their own content."}, {"lang": "es", "value": "Formidable (tambi\u00e9n conocido como node-formidable) 2.1.0 a 3.x (anterior a 3.5.3) utiliza hexoid para evitar la adivinaci\u00f3n de nombres de archivo en ejecutables no confiables. Sin embargo, se ha documentado que hexoid no es criptogr\u00e1ficamente seguro. (Tambi\u00e9n existe un escenario en el que solo es necesario adivinar los dos \u00faltimos caracteres de una cadena hexoid, pero esto no suele ser relevante). NOTA: Esto no implica que, en un caso de uso t\u00edpico, los atacantes puedan explotar cualquier comportamiento hexoid para cargar y ejecutar su propio contenido."}], "lastModified": "2025-04-29T16:15:37.150", "sourceIdentifier": "cve@mitre.org"}