Research Update Enhanced src/linux-hardening/privilege-escal...#2135
Merged
Conversation
Collaborator
Author
🔗 Additional ContextOriginal Blog Post: Content Categories: Based on the analysis, this content was categorized under "Research". Repository Maintenance:
Review Notes:
Bot Version: HackTricks News Bot v1.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Research Update for src/linux-hardening/privilege-escalation/container-security/assessment-and-hardening.md
This PR contains automated research updates including:
Generated by: HackTricks Research Agent
Timestamp: 2026-04-16 03:32:35 UTC
Tool usage
...
🔧 Technical Details
Research update for HackTricks content
🤖 Agent Actions
I’m reading the target page and nearby container-security material first, then I’ll branch into current research and only add content that isn’t already covered elsewhere in HackTricks.
The target page is intentionally short and high-level. I’m checking adjacent container-security pages now so new material stays scoped to “assessment and hardening” instead of duplicating deeper pages on cgroups, seccomp, or specific escapes.
I’ve bounded the overlap: specific escape mechanics already live in adjacent pages. The update will stay on high-value assessment workflow, newer runtime realities, and operator mistakes that materially change attack surface.
I have enough direction now: the likely gap is not another escape PoC, but a modern assessment checklist for rootless/user namespaces, cgroup v2, and Kubernetes-era workload controls that change whether older container breakout advice even applies.
The Kubernetes docs confirmed a few concrete modern checks worth surfacing:
RuntimeDefaultseccomp and AppArmor,allowPrivilegeEscalation: false,runAsNonRoot: true, droppingALLcapabilities, and the newersupplementalGroupsPolicy=Strictbehavior.I’m editing the page now. The changes will stay compact: newer runtime-aware enumeration, Kubernetes-specific posture checks that affect real breakout viability, and updated tool coverage without repeating the dedicated escape pages.
The page is updated. I’m doing a verification pass now for factual sharpness and to trim anything that overreaches the actual APIs or defaults.
I found one overreach in the first pass: I referenced a
pidsresource field in Pod limits, which is not a standard Pod resource field. I’m tightening that and adding the better-supportedsupplementalGroupsPolicycheck instead.Updated assessment-and-hardening.md. The main additions were a modern triage section for rootless/userns and cgroup v2, Kubernetes-specific posture checks that materially affect breakout viability, and updated tooling coverage with
TraceeandInspektor Gadget. I also tightened the hardening guidance around Pod Security Standards and explicitRuntimeDefaultseccomp/AppArmor usage, while keeping the page as a concise assessment field guide instead of duplicating the deeper escape/protection pages.I verified the final content and removed one overreach during review: a non-standard Pod
pidsresource field reference. The page now ends with two external references as requested.Research URLs used:
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.