CVE-2025-64429

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2025-64429", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2025-11-03T22:12:51.364Z", "datePublished": "2025-11-12T21:32:45.663Z", "dateUpdated": "2025-11-13T16:45:43.375Z"}, "containers": {"cna": {"title": "DuckDB Encryption Crypto implementation is vulnerable", "problemTypes": [{"descriptions": [{"cweId": "CWE-327", "lang": "en", "description": "CWE-327: Use of a Broken or Risky Cryptographic Algorithm", "type": "CWE"}]}], "metrics": [{"cvssV4_0": {"attackVector": "NETWORK", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "userInteraction": "NONE", "vulnConfidentialityImpact": "LOW", "vulnIntegrityImpact": "LOW", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "baseScore": 6.9, "baseSeverity": "MEDIUM", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N", "version": "4.0"}}], "references": [{"name": "https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp"}, {"name": "https://github.com/duckdb/duckdb/pull/17275", "tags": ["x_refsource_MISC"], "url": "https://github.com/duckdb/duckdb/pull/17275"}, {"name": "https://duckdb.org/2025/09/16/announcing-duckdb-140.html", "tags": ["x_refsource_MISC"], "url": "https://duckdb.org/2025/09/16/announcing-duckdb-140.html"}, {"name": "https://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20", "tags": ["x_refsource_MISC"], "url": "https://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20"}], "affected": [{"vendor": "duckdb", "product": "duckdb", "versions": [{"version": ">= 1.4.0, < 1.4.2", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2025-11-12T21:32:45.663Z"}, "descriptions": [{"lang": "en", "value": "DuckDB is a SQL database management system. DuckDB implemented block-based encryption of DB on the filesystem starting with DuckDB 1.4.0. There are a few issues related to this implementation. The DuckDB can fall back to an insecure random number generator (pcg32) to generate cryptographic keys or IVs. When clearing keys from memory, the compiler may remove the memset() and leave sensitive data on the heap. By modifying the database header, an attacker could downgrade the encryption mode from GCM to CTR to bypass integrity checks. There may be a failure to check return value on call to OpenSSL `rand_bytes()`. An attacker could use public IVs to compromise the internal state of RNG and determine the randomly generated key used to encrypt temporary files, get access to cryptographic keys if they have access to process memory (e.g. through memory leak),circumvent GCM integrity checks, and/or influence the OpenSSL random number generator and DuckDB would not be able to detect a failure of the generator. Version 1.4.2 has disabled the insecure random number generator by no longer using the fallback to write to or create databases. Instead, DuckDB will now attempt to install and load the OpenSSL implementation in the `httpfs` extension. DuckDB now uses secure MbedTLS primitive to clear memory as recommended and requires explicit specification of ciphers without integrity checks like CTR on `ATTACH`. Additionally, DuckDB now checks the return code."}], "source": {"advisory": "GHSA-vmp8-hg63-v2hp", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2025-11-13T16:45:32.309589Z", "id": "CVE-2025-64429", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2025-11-13T16:45:43.375Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2025-64429", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2025-11-13T16:45:32.309589Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2025-11-13T16:45:39.632Z"}}], "cna": {"title": "DuckDB Encryption Crypto implementation is vulnerable", "source": {"advisory": "GHSA-vmp8-hg63-v2hp", "discovery": "UNKNOWN"}, "metrics": [{"cvssV4_0": {"version": "4.0", "baseScore": 6.9, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "LOW"}}], "affected": [{"vendor": "duckdb", "product": "duckdb", "versions": [{"status": "affected", "version": ">= 1.4.0, < 1.4.2"}]}], "references": [{"url": "https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp", "name": "https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/duckdb/duckdb/pull/17275", "name": "https://github.com/duckdb/duckdb/pull/17275", "tags": ["x_refsource_MISC"]}, {"url": "https://duckdb.org/2025/09/16/announcing-duckdb-140.html", "name": "https://duckdb.org/2025/09/16/announcing-duckdb-140.html", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20", "name": "https://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "DuckDB is a SQL database management system. DuckDB implemented block-based encryption of DB on the filesystem starting with DuckDB 1.4.0. There are a few issues related to this implementation. The DuckDB can fall back to an insecure random number generator (pcg32) to generate cryptographic keys or IVs. When clearing keys from memory, the compiler may remove the memset() and leave sensitive data on the heap. By modifying the database header, an attacker could downgrade the encryption mode from GCM to CTR to bypass integrity checks. There may be a failure to check return value on call to OpenSSL `rand_bytes()`. An attacker could use public IVs to compromise the internal state of RNG and determine the randomly generated key used to encrypt temporary files, get access to cryptographic keys if they have access to process memory (e.g. through memory leak),circumvent GCM integrity checks, and/or influence the OpenSSL random number generator and DuckDB would not be able to detect a failure of the generator. Version 1.4.2 has disabled the insecure random number generator by no longer using the fallback to write to or create databases. Instead, DuckDB will now attempt to install and load the OpenSSL implementation in the `httpfs` extension. DuckDB now uses secure MbedTLS primitive to clear memory as recommended and requires explicit specification of ciphers without integrity checks like CTR on `ATTACH`. Additionally, DuckDB now checks the return code."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-327", "description": "CWE-327: Use of a Broken or Risky Cryptographic Algorithm"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2025-11-12T21:32:45.663Z"}}}, "cveMetadata": {"cveId": "CVE-2025-64429", "state": "PUBLISHED", "dateUpdated": "2025-11-13T16:45:43.375Z", "dateReserved": "2025-11-03T22:12:51.364Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2025-11-12T21:32:45.663Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "duckdb", "vendor": "duckdb", "versions": [{"status": "affected", "version": ">= 1.4.0, < 1.4.2"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:duckdb:duckdb:*:*:*:*:*:*:*:*", "matchCriteriaId": "4F45224E-AE97-4601-86D7-163A4E531A60", "versionEndExcluding": "1.4.2", "versionStartIncluding": "1.4.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "DuckDB is a SQL database management system. DuckDB implemented block-based encryption of DB on the filesystem starting with DuckDB 1.4.0. There are a few issues related to this implementation. The DuckDB can fall back to an insecure random number generator (pcg32) to generate cryptographic keys or IVs. When clearing keys from memory, the compiler may remove the memset() and leave sensitive data on the heap. By modifying the database header, an attacker could downgrade the encryption mode from GCM to CTR to bypass integrity checks. There may be a failure to check return value on call to OpenSSL `rand_bytes()`. An attacker could use public IVs to compromise the internal state of RNG and determine the randomly generated key used to encrypt temporary files, get access to cryptographic keys if they have access to process memory (e.g. through memory leak),circumvent GCM integrity checks, and/or influence the OpenSSL random number generator and DuckDB would not be able to detect a failure of the generator. Version 1.4.2 has disabled the insecure random number generator by no longer using the fallback to write to or create databases. Instead, DuckDB will now attempt to install and load the OpenSSL implementation in the `httpfs` extension. DuckDB now uses secure MbedTLS primitive to clear memory as recommended and requires explicit specification of ciphers without integrity checks like CTR on `ATTACH`. Additionally, DuckDB now checks the return code."}, {"lang": "es", "value": "DuckDB es un sistema de gesti\u00f3n de bases de datos SQL. DuckDB implement\u00f3 el cifrado basado en bloques de la base de datos en el sistema de archivos a partir de DuckDB 1.4.0. Existen algunos problemas relacionados con esta implementaci\u00f3n. DuckDB puede recurrir a un generador de n\u00fameros aleatorios inseguro (pcg32) para generar claves criptogr\u00e1ficas o IVs. Al borrar claves de la memoria, el compilador puede eliminar memset() y dejar datos sensibles en el heap. Al modificar el encabezado de la base de datos, un atacante podr\u00eda degradar el modo de cifrado de GCM a CTR para eludir las comprobaciones de integridad. Puede haber un fallo al verificar el valor de retorno en la llamada a OpenSSL rand_bytes(). Un atacante podr\u00eda usar IVs p\u00fablicos para comprometer el estado interno del RNG y determinar la clave generada aleatoriamente utilizada para cifrar archivos temporales, obtener acceso a claves criptogr\u00e1ficas si tiene acceso a la memoria del proceso (por ejemplo, a trav\u00e9s de una fuga de memoria), eludir las comprobaciones de integridad de GCM y/o influir en el generador de n\u00fameros aleatorios de OpenSSL y DuckDB no podr\u00eda detectar un fallo del generador. La versi\u00f3n 1.4.2 ha deshabilitado el generador de n\u00fameros aleatorios inseguro al dejar de usar el recurso alternativo para escribir o crear bases de datos. En su lugar, DuckDB ahora intentar\u00e1 instalar y cargar la implementaci\u00f3n de OpenSSL en la extensi\u00f3n httpfs. DuckDB ahora utiliza la primitiva segura MbedTLS para borrar la memoria seg\u00fan lo recomendado y requiere la especificaci\u00f3n expl\u00edcita de cifrados sin comprobaciones de integridad como CTR en ATTACH. Adem\u00e1s, DuckDB ahora verifica el c\u00f3digo de retorno."}], "id": "CVE-2025-64429", "lastModified": "2026-10-19T13:10:00.110", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "LOW", "integrityImpact": "LOW", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 2.5, "source": "nvd@nist.gov", "type": "Primary"}], "cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "NONE", "attackVector": "NETWORK", "availabilityRequirement": "NOT_DEFINED", "baseScore": 6.9, "baseSeverity": "MEDIUM", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "NONE", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/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", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "LOW", "vulnIntegrityImpact": "LOW", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-64429", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2025-11-13T16:45:32.309589Z", "version": "2.0.3"}}]}, "published": "2025-11-12T22:15:49.813", "references": [{"source": "security-advisories@github.com", "tags": ["Release Notes"], "url": "https://duckdb.org/2025/09/16/announcing-duckdb-140.html"}, {"source": "security-advisories@github.com", "tags": ["Product"], "url": "https://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20"}, {"source": "security-advisories@github.com", "tags": ["Patch"], "url": "https://github.com/duckdb/duckdb/pull/17275"}, {"source": "security-advisories@github.com", "tags": ["Vendor Advisory"], "url": "https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-327"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{"bugzilla": {"description": "duckdb: Encryption Crypto implementation is vulnerable", "id": "2414694", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2414694"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.5", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "status": "draft"}, "cwe": "CWE-327", "details": ["A vulnerability was found in DuckDB\u2019s database encryption design. In certain situations, DuckDB could generate encryption keys using a weak random number generator, fail to reliably wipe keys from memory, accept manipulated database headers that disable integrity protection, or miss detecting failures when generating random bytes. These issues could allow an attacker with the ability to influence database files or access process memory to predict encryption keys, bypass integrity checks, or access sensitive information protected by DuckDB\u2019s encryption features."], "mitigation": {"lang": "en:us", "value": "No mitigation is currently required or applicable, as the affected code is not shipped in supported Red Hat products."}, "name": "CVE-2025-64429", "package_state": [{"cpe": "cpe:/a:redhat:openshift_ai", "fix_state": "Not affected", "package_name": "rhoai/odh-feature-server-rhel9", "product_name": "Red Hat OpenShift AI (RHOAI)"}], "public_date": "2025-11-12T21:32:45Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2025-64429\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-64429\nhttps://duckdb.org/2025/09/16/announcing-duckdb-140.html\nhttps://github.com/duckdb/duckdb/blob/029a5b87ff5b1cd22f7f9717d48cd8830d00807c/src/common/random_engine.cpp#L20\nhttps://github.com/duckdb/duckdb/pull/17275\nhttps://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp"], "statement": "~~~\nThis vulnerability was introduced when DuckDB added block-based on-disk encryption in the 1.4.0 release. The odh-feature-server-rhel9 container shipped with Red Hat OpenShift AI includes DuckDB 1.1.3, which does not contain this encryption feature and therefore is not affected by this issue.\n~~~", "threat_severity": "Moderate"}

{"created": "2025-11-13T09:52:07.227491+00:00", "updated": "2025-11-13T09:52:07.227529+00:00", "vendors": ["duckdb", "duckdb$PRODUCT$duckdb"]}