Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-25165: getHostByName Function Information Disclosure

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.76% (FIRST EPSS); higher than 55.8% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: helm.sh/helm/v3 (Go) 3.11.1; helm (openSUSE:Leap 15.4) 3.11.1-150000.1.16.1; terraform-provider-helm (openSUSE:Leap 15.4) 2.9.0-150200.6.8.1.

Low priority for now. Upgrade to helm.sh/helm/v3 (Go) 3.11.1; helm (openSUSE:Leap 15.4) 3.11.1-150000.1.16.1; terraform-provider-helm (openSUSE:Leap 15.4) 2.9.0-150200.6.8.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Helm is a tool that streamlines installing and managing Kubernetes applications.`getHostByName` is a Helm template function introduced in Helm v3. The function is able to accept a hostname and return an IP address for that hostname. To get the IP address the function performs a DNS lookup. The DNS lookup happens when used with `helm install|upgrade|template` or when the Helm SDK is used to render a chart. Information passed into the chart can be disclosed to the DNS servers used to lookup the IP address. For example, a malicious chart could inject `getHostByName` into a chart in order to disclose values to a malicious DNS server. The issue has been fixed in Helm 3.11.1. Prior to using a chart with Helm verify the `getHostByName` function is not being used in a template to disclose any information you do not want passed to DNS servers.

MediumCVSS 4.3 · v3.1—No exploit Fix available
Published
Feb 8, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 55th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.3
CNA · GitHub_M
4.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-25165

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for helm records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
helmhelm

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • helm helm3.0.0 and later · before 3.11.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • helm helm

    • >= 3.0.0, < 3.11.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gohelm.sh/helm/v3from 3.0.0 · before 3.11.13.11.1
Gohelm.sh/helm/v3before 3.11.13.11.1
openSUSE:Leap 15.4helmbefore 3.11.1-150000.1.16.13.11.1-150000.1.16.1
openSUSE:Leap 15.4terraform-provider-helmbefore 2.9.0-150200.6.8.12.9.0-150200.6.8.1
openSUSE:Leap 15.4trivybefore 0.37.3-bp154.2.9.10.37.3-bp154.2.9.1
openSUSE:Tumbleweedcilium-clibefore 0.12.13-1.10.12.13-1.1
openSUSE:Tumbleweedhelmbefore 3.11.1-1.13.11.1-1.1
openSUSE:Tumbleweedhelm3before 3.19.2-1.13.19.2-1.1
openSUSE:Tumbleweedhelmfilebefore 0.150.0-2.10.150.0-2.1
openSUSE:Tumbleweedk9sbefore 0.27.3-1.10.27.3-1.1
openSUSE:Tumbleweednovabefore 3.6.1-1.13.6.1-1.1
openSUSE:Tumbleweedplutobefore 5.13.3-1.15.13.3-1.1
openSUSE:Tumbleweedterraform-provider-helmbefore 2.9.0-1.12.9.0-1.1
openSUSE:Tumbleweedtrivybefore 0.37.3-1.10.37.3-1.1
SUSE:Linux Enterprise Module for Containers 15 SP4helmbefore 3.11.1-150000.1.16.13.11.1-150000.1.16.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP1terraform-provider-helmbefore 2.9.0-150100.3.6.32.9.0-150100.3.6.3
SUSE:Linux Enterprise Module for Public Cloud 15 SP2terraform-provider-helmbefore 2.9.0-150200.6.8.12.9.0-150200.6.8.1
SUSE:Package Hub 15 SP4trivybefore 0.37.3-bp154.2.9.10.37.3-bp154.2.9.1

Same product

helm: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-18658In Helm 2.x before 2.15.2, commands that deal with loading a chart as a directory or packaging a chart provide an opportunity for a…
    40Plan
  • CVE-2019-1010275helm Before 2.7.2 is affected by: CWE-295: Improper Certificate Validation.
    39Monitor
  • CVE-2025-53547Helm Chart Dependency Updating With Malicious Chart.yaml Content And Symlink Can Lead To Code Execution
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-23525Dec 15, 2022 · Helm vulnerable to Denial of service via NULL Pointer Dereference
    30Monitor
  • ← EarlierCVE-2022-23526Dec 15, 2022 · Helm contains Denial of service through schema file
    30Monitor
  • Later →CVE-2024-25620Feb 14, 2024 · Dependency management path traversal in helm
    25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:helm.sh/helm/v33.11.1Package registry (OSV)
opensuse:cilium-cli0.12.13-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:helm3.11.1-150000.1.16.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:helm33.19.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:helmfile0.150.0-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:k9s0.27.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nova3.6.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:pluto5.13.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:terraform-provider-helm2.9.0-150200.6.8.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:trivy0.37.3-bp154.2.9.1 · openSUSE:Leap 15.4Package registry (OSV)
suse:helm3.11.1-150000.1.16.1 · SUSE:Linux Enterprise Module for Containers 15 SP4Package registry (OSV)
suse:terraform-provider-helm2.9.0-150200.6.8.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP2Package registry (OSV)
suse:trivy0.37.3-bp154.2.9.1 · SUSE:Package Hub 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records