🐛 users: skip /etc/passwd entries with unparseable uid/gid

[tas50]

Bug

ParseEtcPasswd in users/etcpasswd.go:

uid, err := strconv.ParseInt(m[2], 10, 0)
if err != nil {
    log.Error().Err(err).Str("user", m[0]).Msg("could not parse uid")
}
gid, err := strconv.ParseInt(m[3], 10, 0)
if err != nil {
    log.Error().Err(err).Str("user", m[0]).Msg("could not parse gid")
}
users = append(users, &User{ ... Uid: uid, Gid: gid, ... })

The error is logged but not acted on: on a parse failure uid/gid keep their zero value and the user is still appended. A malformed /etc/passwd line therefore surfaces as a uid 0 / gid 0 (root) account — the worst possible sentinel for an inventory/security tool (the sibling shadow.go parser correctly returns an error in the same situation).

Fix

Skip the entry (with a warning log) when uid or gid can't be parsed, so a corrupt line is dropped rather than fabricating root. Added a regression test with malformed uid and gid lines.

🤖 Generated with Claude Code

https://claude.ai/code/session_015U1ocAxfcBhVYi3f9JnyZZ

---

Generated by Claude Code

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[mondoo-code-review]

Fixes a bug where malformed /etc/passwd entries with non-numeric uid/gid were silently treated as uid 0 (root).

[github-actions]

Test Results

11 154 tests  +1   11 147 ✅ +1   3m 33s ⏱️ - 1m 47s
   545 suites ±0        7 💤 ±0 
    40 files   ±0        0 ❌ ±0 

Results for commit 5614f7d. ± Comparison against base commit a92a575.

♻️ This comment has been updated with latest results.