What is GHSA-87MP-XC4X-X8RH?

GHSA-87MP-XC4X-X8RH is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in asymmetricrypt/asymmetricrypt (composer), affecting versions <= 0.3.0. No fixed version is listed yet. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.

Which versions of asymmetricrypt/asymmetricrypt are affected by GHSA-87MP-XC4X-X8RH?

asymmetricrypt/asymmetricrypt (composer) versions <= 0.3.0 is affected.

Is there a fix for GHSA-87MP-XC4X-X8RH?

No fixed version is listed for GHSA-87MP-XC4X-X8RH yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-87MP-XC4X-X8RH exploitable, and should I be worried?

Whether GHSA-87MP-XC4X-X8RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-87MP-XC4X-X8RH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-87MP-XC4X-X8RH in asymmetricrypt/asymmetricrypt

Q: Which versions of asymmetricrypt/asymmetricrypt are affected by GHSA-87MP-XC4X-X8RH?

asymmetricrypt/asymmetricrypt (composer) versions <= 0.3.0 is affected.

Q: Is there a fix for GHSA-87MP-XC4X-X8RH?

No fixed version is listed for GHSA-87MP-XC4X-X8RH yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-87MP-XC4X-X8RH exploitable, and should I be worried?

Whether GHSA-87MP-XC4X-X8RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-87MP-XC4X-X8RH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-87MP-XC4X-X8RH?

No fixed version is listed yet. In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.

Summary

asymmetricrypt/asymmetricrypt Padding Oracle Vulnerability in RSA Encryption

The encryption and decryption process were vulnerable against the Bleichenbacher's attack, which is a padding oracle vulnerability disclosed in the 98'.
The issue was about the wrong padding utilized, which allowed to retrieve the encrypted content.
The 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).

A fix for this vulnerability was merged at https://github.com/Cosmicist/AsymmetriCrypt/pull/5/commits/a0318cfc5022f2a7715322dba3ff91d475ace7c6.

Impact

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

Affected versions

asymmetricrypt/asymmetricrypt (<= 0.3.0)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for GHSA-87MP-XC4X-X8RH yet.

In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-87MP-XC4X-X8RH? GHSA-87MP-XC4X-X8RH is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in asymmetricrypt/asymmetricrypt (composer), affecting versions <= 0.3.0. No fixed version is listed yet. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
Which versions of asymmetricrypt/asymmetricrypt are affected by GHSA-87MP-XC4X-X8RH? asymmetricrypt/asymmetricrypt (composer) versions <= 0.3.0 is affected.
Is there a fix for GHSA-87MP-XC4X-X8RH? No fixed version is listed for GHSA-87MP-XC4X-X8RH yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-87MP-XC4X-X8RH exploitable, and should I be worried? Whether GHSA-87MP-XC4X-X8RH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-87MP-XC4X-X8RH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-87MP-XC4X-X8RH? No fixed version is listed yet. In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.