{"answers":{"affected":"2 open source packages ship an affected version, including ascon_aead.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27498 exists.","fix":"Upgrade ascon_aead to 0.4.3 or later.","what":"CVE-2025-27498 is a medium-severity vulnerability in RustCrypto AEADs, published on 3 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-27498 and fix it if it is affected.\n\nWhat it is: CVE-2025-27498 is a medium-severity vulnerability in RustCrypto AEADs, published on 3 Mar 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27498 exists.\n\nAffected packages and fixed versions:\n- ascon_aead (crates.io): affected all versions; fixed in 0.4.3\n- ascon_aead (crates.io): affected all versions; fixed in 0.4.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-27498/ (Markdown: https://insights.sbomify.com/CVE-2025-27498/index.md)","id":"CVE-2025-27498","markdown":"https://insights.sbomify.com/CVE-2025-27498/index.md","name":"CVE-2025-27498","record":{"aliases":["GHSA-r38m-44fw-h886","UBUNTU-CVE-2025-27498"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust AES-GCM library","requires_auth":"none","summary":"Attackers can recover plaintext from failed AEAD decryption attempts in the RustCrypto AES-GCM library due to improper buffer clearing.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"aes-gcm is a pure Rust implementation of the AES-GCM. In decrypt_in_place_detached, the decrypted ciphertext (which is the correct ciphertext) is exposed even if the tag is incorrect. This is because in decrypt_inplace in asconcore.rs, tag verification causes an error to be returned with the plaintext contents still in buffer. The vulnerability is fixed in 0.4.3.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AEADs/ascon-aead: Plaintext exposed in decrypt_in_place_detached even on tag verification failure","id":"CVE-2025-27498","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"WeGIA has a stored Cross-Site Scripting (XSS) in 'processa_edicao_socio.php' via the 'socio_nome' parameter","id":"CVE-2025-27499"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"ascon_aead","purl":null,"source":"GHSA-r38m-44fw-h886"},{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"ascon_aead","purl":"pkg:cargo/ascon_aead","source":"GHSA-r38m-44fw-h886"}],"prev":{"headline":"OpenDJ Denial of Service (Dos) using alias loop","id":"CVE-2025-27497"},"products":["AEADs"],"published":"2025-03-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-03","vendors":["RustCrypto"]},"summary":"Attackers can recover plaintext from failed AEAD decryption attempts in the RustCrypto AES-GCM library due to improper buffer clearing.","url":"https://insights.sbomify.com/CVE-2025-27498/"}