CVE-2025-47285

{"id": "CVE-2025-47285", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 2.9, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "LOW", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "PROOF_OF_CONCEPT", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-05-15T18:15:38.177", "references": [{"url": "https://github.com/vyperlang/vyper/blob/68b68c4b30c5ef2f312b4674676170b8a6eaa316/vyper/builtins/functions.py#L560-L562", "source": "security-advisories@github.com"}, {"url": "https://github.com/vyperlang/vyper/pull/4644", "source": "security-advisories@github.com"}, {"url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-qhr6-mgqr-mchm", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-691"}]}], "descriptions": [{"lang": "en", "value": "Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, `concat()` may skip evaluation of side effects when the length of an argument is zero. This is due to a fastpath in the implementation which skips evaluation of argument expressions when their length is zero. In practice, it would be very unusual in user code to construct zero-length bytestrings using an expression with side-effects, since zero-length bytestrings are typically constructed with the empty literal `b\"\"`; the only way to construct an empty bytestring which has side effects would be with the ternary operator introduced in v0.3.8, e.g. `b\"\" if self.do_some_side_effect() else b\"\"`. The fix is available in pull request 4644 and expected to be part of the 0.4.2 release. As a workaround, don't have side effects in expressions which construct zero-length bytestrings."}, {"lang": "es", "value": "Vyper es el lenguaje de programaci\u00f3n Pythonic para la M\u00e1quina Virtual de Ethereum. En versiones hasta la 0.4.2rc1 (incluida), `concat()` puede omitir la evaluaci\u00f3n de efectos secundarios cuando la longitud de un argumento es cero. Esto se debe a una ruta r\u00e1pida en la implementaci\u00f3n que omite la evaluaci\u00f3n de expresiones de argumentos cuando su longitud es cero. En la pr\u00e1ctica, ser\u00eda muy inusual en el c\u00f3digo de usuario construir cadenas de bytes de longitud cero utilizando una expresi\u00f3n con efectos secundarios, ya que estas cadenas se construyen t\u00edpicamente con el literal vac\u00edo `b\"\"`; la \u00fanica manera de construir una cadena de bytes vac\u00eda con efectos secundarios ser\u00eda con el operador ternario introducido en la v0.3.8, por ejemplo, `b\"\" if self.do_some_side_effect() else b\"\"`. La correcci\u00f3n est\u00e1 disponible en la solicitud de incorporaci\u00f3n de cambios 4644 y se espera que forme parte de la versi\u00f3n 0.4.2. Como workaround, no se deben incluir efectos secundarios en expresiones que construyen cadenas de bytes de longitud cero."}], "lastModified": "2025-05-16T14:43:26.160", "sourceIdentifier": "security-advisories@github.com"}