Join our Newsletter — 33% off our NHI Course

Why does Local Path Provisioner path templating reach the host?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Path templating in Rancher Local Path Provisioner lets user-controlled metadata reach the host filesystem, according to Orca Security. K3s storage now needs tighter governance around path construction because resolved paths can become node-level read, write, or delete operations.

Editorial analysis by NHI Mgmt Group, based on content published by Orca Security: “Path Traversal in Rancher Local Path Provisioner Enables Host Filesystem Compromise Across K3s Clusters”.

Key questions

Q: Why does this vulnerability create host risk instead of just broken storage isolation?

A: Because the provisioner does not stop at path calculation.

Q: What signs show that a K3s cluster is exposed to this storage flaw?

A: Look for StorageClasses that define pathPattern, especially if they reference PVC annotations or other user-controlled fields.

Q: What breaks when a StorageClass path template accepts user-controlled metadata?

A: The trust boundary breaks at the point where Kubernetes metadata becomes a host filesystem path.

Practitioner guidance

  • Audit every StorageClass path template Review pathPattern usage for any reference to PVC names, namespaces, labels, or annotations, and remove user-controlled inputs from host path construction.
  • Block traversal sequences in admission controls Use admission policy to reject StorageClass values containing ../ or equivalent traversal patterns before they ever reach the provisioner.
  • Restrict who can create or modify StorageClasses Limit StorageClass administration to trusted cluster operators and treat that permission as host-impacting authority, not routine namespace access.

Bottom line: The flaw is a path-joining and trust-boundary problem, not just a storage bug, because user-controlled metadata can reach the host filesystem.

Glossary terms: StorageClass Templating, HostPath-backed Provisioning, Path Traversal in Provisioning Logic, Host-Level Identity Boundary

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Default storage provisioning can become an identity boundary when it accepts user-controlled path templates: The vulnerable behavior is not simply a bad filesystem join. It is a governance failure in how a cluster decides who can influence where storage lands on the host. That boundary matters because the rendered path is derived from Kubernetes objects, which means storage authorization and host authorization are now entangled. Practitioners should treat StorageClass templating as a trust decision, not a convenience feature.

A few things that frame the scale:

  • The average time to mitigate a leaked secret is 36 hours, highlighting the operational burden of manual remediation processes, according to the 2024 State of Secrets Management Survey.
  • The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to the State of Secrets in AppSec.

A question worth separating out:

Q: Should teams treat default K3s storage as lower risk than custom storage classes?

A: No. Default K3s installs reduce the attack surface only when the provisioner uses its built-in, non-user-controlled path template. Once operators introduce custom templating or unsafe path handling, the same default backend can become a host-level exposure path.

👉 Read our full editorial: K3s storage traversal turns a default provisioner into host risk



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.