Helm up to 3.10.2 Repository Index File null pointer dereference

Summaryinfo

A vulnerability marked as problematic has been reported in Helm up to 3.10.2. This affects an unknown part of the component Repository Index File Handler. Performing a manipulation results in null pointer dereference. This vulnerability is reported as CVE-2022-23525. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Helm up to 3.10.2. This affects an unknown code of the component Repository Index File Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:

Helm is a tool for managing Charts, pre-configured Kubernetes resources. Versions prior to 3.10.3 are subject to NULL Pointer Dereference in the _repo_package. The _repo_ package contains a handler that processes the index file of a repository. For example, the Helm client adds references to chart repositories where charts are managed. The _repo_ package parses the index file of the repository and loads it into structures Go can work with. Some index files can cause array data structures to be created causing a memory violation. Applications that use the _repo_ package in the Helm SDK to parse an index file can suffer a Denial of Service when that input causes a panic that cannot be recovered from. The Helm Client will panic with an index file that causes a memory violation panic. Helm is not a long running service so the panic will not affect future uses of the Helm client. This issue has been patched in 3.10.3. SDK users can validate index files that are correctly formatted before passing them to the _repo_ functions.

The weakness was disclosed 12/15/2022 as GHSA-53c4-hhmh-vw5q. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-23525 since 01/19/2022. Neither technical details nor an exploit are publicly available.

Upgrading to version 3.10.3 eliminates this vulnerability. Applying the patch 638ebffbc2e445156f3978f02fd83d9af1e56f5b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Helm

Version

• 3.10.0
• 3.10.1
• 3.10.2

License

• open-source

Website

• Product: https://github.com/helm/helm/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion