CVE-2024-1394

A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.
Configurations

No configuration.

History

27 Apr 2024, 01:15

Type Values Removed Values Added
References
  • () https://access.redhat.com/errata/RHSA-2024:1897 -

25 Apr 2024, 21:15

Type Values Removed Values Added
References
  • () https://access.redhat.com/errata/RHSA-2024:1763 -

16 Apr 2024, 13:15

Type Values Removed Values Added
References
  • () https://github.com/golang-fips/openssl/commit/85d31d0d257ce842c8a1e63c4d230ae850348136 -
  • () https://github.com/microsoft/go-crypto-openssl/commit/104fe7f6912788d2ad44602f77a0a0a62f1f259f -
  • () https://pkg.go.dev/vuln/GO-2024-2660 -
  • () https://vuln.go.dev/ID/GO-2024-2660.json -

03 Apr 2024, 18:15

Type Values Removed Values Added
References
  • () https://access.redhat.com/errata/RHSA-2024:1566 -
  • () https://access.redhat.com/errata/RHSA-2024:1567 -

03 Apr 2024, 13:16

Type Values Removed Values Added
References
  • () https://access.redhat.com/errata/RHSA-2024:1574 -

03 Apr 2024, 00:15

Type Values Removed Values Added
References
  • () https://access.redhat.com/errata/RHSA-2024:1561 -
  • () https://access.redhat.com/errata/RHSA-2024:1563 -
  • () https://access.redhat.com/errata/RHSA-2024:1640 -
  • () https://access.redhat.com/errata/RHSA-2024:1644 -
  • () https://access.redhat.com/errata/RHSA-2024:1646 -

26 Mar 2024, 00:15

Type Values Removed Values Added
Summary
  • (es) Se encontró una falla de pérdida de memoria en Golang en el código de cifrado/descifrado RSA, lo que podría conducir a una vulnerabilidad de agotamiento de recursos mediante entradas controladas por el atacante. La pérdida de memoria ocurre en github.com/golang-fips/openssl/openssl/rsa.go#L113. Los objetos filtrados son pkey? y ctx?. Esa función utiliza parámetros de retorno con nombre para liberar pkey? y ctx? si hay un error al inicializar el contexto o al configurar las diferentes propiedades. Todas las declaraciones de devolución relacionadas con casos de error siguen el patrón "return nil, nil, fail(...)", lo que significa que pkey? y ctx? serán nulos dentro de la función diferida que debería liberarlos.
References
  • () https://access.redhat.com/errata/RHSA-2024:1501 -
  • () https://access.redhat.com/errata/RHSA-2024:1502 -

21 Mar 2024, 19:15

Type Values Removed Values Added
Summary (en) A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs?. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey? and ctx?. That function uses named return parameters to free pkey? and ctx? if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey? and ctx? will be nil inside the deferred function that should free them. (en) A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them.
References
  • () https://access.redhat.com/errata/RHSA-2024:1468 -
  • () https://access.redhat.com/errata/RHSA-2024:1472 -

21 Mar 2024, 15:24

Type Values Removed Values Added
Summary (en) A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs​. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey​ and ctx​. That function uses named return parameters to free pkey​ and ctx​ if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey​ and ctx​ will be nil inside the deferred function that should free them. (en) A memory leak flaw was found in Golang in the RSA encrypting/decrypting code, which might lead to a resource exhaustion vulnerability using attacker-controlled inputs?. The memory leak happens in github.com/golang-fips/openssl/openssl/rsa.go#L113. The objects leaked are pkey? and ctx?. That function uses named return parameters to free pkey? and ctx? if there is an error initializing the context or setting the different properties. All return statements related to error cases follow the "return nil, nil, fail(...)" pattern, meaning that pkey? and ctx? will be nil inside the deferred function that should free them.

21 Mar 2024, 13:00

Type Values Removed Values Added
New CVE

Information

Published : 2024-03-21 13:00

Updated : 2024-04-27 01:15


NVD link : CVE-2024-1394

Mitre link : CVE-2024-1394

CVE.ORG link : CVE-2024-1394


JSON object : View

Products Affected

No product.

CWE
CWE-401

Missing Release of Memory after Effective Lifetime