Skip to content

Memory leaks in code encrypting and verifying RSA payloads

High severity GitHub Reviewed Published Mar 20, 2024 in golang-fips/openssl • Updated Aug 21, 2024

Package

gomod github.com/golang-fips/go (Go)

Affected versions

<= 1.22.1

Patched versions

None
gomod github.com/golang-fips/openssl/openssl (Go)
<= 0
None
gomod github.com/golang-fips/openssl/v2 (Go)
<= 2.0.0
2.0.1
gomod github.com/microsoft/go-crypto-openssl (Go)
<= 0.2.8
None
gomod github.com/microsoft/go-crypto-openssl/openssl (Go)
<= 0.2.8
0.2.9

Description

Using crafted public RSA keys which are not compliant with SP 800-56B can cause a small memory leak when encrypting and verifying payloads.

An attacker can leverage this flaw to gradually erode available memory to the point where the host crashes for lack of resources. Upon restart the attacker would have to begin again, but nevertheless there is the potential to deny service.

References

@gdams gdams published to golang-fips/openssl Mar 20, 2024
Published to the GitHub Advisory Database Mar 20, 2024
Reviewed Mar 20, 2024
Published by the National Vulnerability Database Mar 21, 2024
Last updated Aug 21, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.069%
(31st percentile)

Weaknesses

CVE ID

CVE-2024-1394

GHSA ID

GHSA-78hx-gp6g-7mj6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.