{"answers":{"affected":"2 open source packages ship an affected version, including asymmetricrypt/asymmetricrypt.","exploited":"There is no known exploitation of GHSA-87mp-xc4x-x8rh in the wild and no public exploit code.","fix":"No fix has been published for GHSA-87mp-xc4x-x8rh yet. Limit exposure of the affected software until one is available.","what":"GHSA-87mp-xc4x-x8rh is a vulnerability in asymmetricrypt/asymmetricrypt, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-87mp-xc4x-x8rh and fix it if it is affected.\n\nWhat it is: GHSA-87mp-xc4x-x8rh is a vulnerability in asymmetricrypt/asymmetricrypt, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-87mp-xc4x-x8rh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- asymmetricrypt/asymmetricrypt (Packagist): affected all versions up to 0.3.0; no fix listed\n- asymmetricrypt/asymmetricrypt (Packagist): affected all versions up to 0.3.0; no fix listed\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/GHSA-87mp-xc4x-x8rh/ (Markdown: https://insights.sbomify.com/GHSA-87mp-xc4x-x8rh/index.md)","id":"GHSA-87mp-xc4x-x8rh","markdown":"https://insights.sbomify.com/GHSA-87mp-xc4x-x8rh/index.md","name":"GHSA-87mp-xc4x-x8rh","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PHP RSA encryption library","requires_auth":"none","summary":"An attacker can decrypt RSA ciphertexts via a padding oracle attack due to insecure PKCS#1 v1.5 padding usage in the AsymmetriCrypt library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The encryption and decryption process were vulnerable against the Bleichenbacher's attack, which is a padding oracle vulnerability disclosed in the 98'.\nThe issue was about the wrong padding utilized, which allowed to retrieve the encrypted content.\nThe OPENSSL_PKCS1_PADDING version, aka PKCS v1.5 was vulnerable (is the one set by default when using openssl_* methods), while the PKCS v2.0 isn't anymore (it's also called OAEP).\n\nA fix for this vulnerability was merged at https://github.com/Cosmicist/AsymmetriCrypt/pull/5/commits/a0318cfc5022f2a7715322dba3ff91d475ace7c6.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"asymmetricrypt/asymmetricrypt Padding Oracle Vulnerability in RSA Encryption","id":"GHSA-87mp-xc4x-x8rh","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"asymmetricrypt/asymmetricrypt","purl":null,"source":"GHSA-87mp-xc4x-x8rh"},{"ecosystem":"Packagist","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"asymmetricrypt/asymmetricrypt","purl":"pkg:composer/asymmetricrypt/asymmetricrypt","source":"GHSA-87mp-xc4x-x8rh"}],"products":null,"published":"2024-05-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can decrypt RSA ciphertexts via a padding oracle attack due to insecure PKCS#1 v1.5 padding usage in the AsymmetriCrypt library.","url":"https://insights.sbomify.com/GHSA-87mp-xc4x-x8rh/"}