CriticalOS hardeningBLWK-FS-001

A sensitive system file is world-writable

What this means

“‹path›” is world-writable (mode ‹mode octal›). Any local user — or any process running as any user — can modify it directly.

How to fix it

chmod o-w ‹path›

Check it yourself

Run a scan and look for BLWK-FS-001 in the results:

bulwark scan

Installed the standalone CLI package instead of the app? The command is bulwarkctl.

How Bulwark decides

Bulwark reads file_permissions and reports this check when:

world_writable == true

If a value can't be read, Bulwark reports the check as undetermined rather than passing it. View the rule source.

References

• CIS Benchmark 6.1
• MITRE ATT&CK T1222

Related checks

• Cron entry runs a downloader piped to a shell · BLWK-ACCT-001
• Password maximum age is excessively long · BLWK-ACCT-002
• Password minimum age is zero · BLWK-ACCT-003
• Password hashing rounds are not explicitly configured · BLWK-ACCT-004
• Default UMASK is not explicitly configured · BLWK-ACCT-005
• /etc/shadow is world-readable · BLWK-FS-002