deepfence / deepfence/ThreatMapper

Vulnerability Scan Failing with Minimal Context

Open
#172 6 comments 0 reactions 1 assignee Claimed by @saurabh2253 View on GitHub
bug needs-triage
Dominant language
TypeScript
Stars
5.3k
Forks
631
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Deployed a single agent on the same node running the dockers for the console which is itself an Arch LXC inside an Arch host.
Scans initiated with any option set possible fail with `Vulnerability scan failed. Scan was interrupted. Please restart.` which is not helpful. OS package scans can't be disabled and i highly doubt ThreatMapper has `arch-audit` integration... So my _guess_ would be its failing on OS packages for lack of `pacman` or `arch-audit` interface/data (Arch has packagekit if thats a viable approach, but it does add an extra dependency to the system being scanned).
The LXC running all of this is privileged with nesting for the dockers, but there's no debugfs and sysfs in general is more locked down than ThreatMapper seems to presume (modern Grsecurity system) so i had to comment those pieces out of the docker-compose and agent script.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.