- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
When the Agents Attack
A Live Look at Agentic Exposure Validation
Bridge the CAASM Gap
with Exposure Management
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
CheckMates Go:
CheckMates Fest
Recently we created a separate User for a Management Tool. It worked normally until yesterday. Since Yesterday the User isn't able to do scp or something else. If the User logs in the following Message appears:
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
-bash: /dev/null: Permission denied
Also if the User runs the Command SCP:
scp
Couldn't open /dev/null: Permission denied
The User has the Bash Shell as default and the AdminRole is assigned.
What permissions should the /dev/null directory normally have?
[Expert@mgmt:0]# ls -la /dev/null
crw-rw-rw- 1 admin root 1, 3 Nov 7 13:54 /dev/null
I assume a chmod 666 /dev/null in expert mode would resolve this?
Is /dev/null mentioned anywhere in the user profile?
No its not mentioned in bash_profile or bashrc
I would try to setup a second account with the same settings and see if the issue is reproducible. If it is, open a TAC case.
The Problem also happens with a new created account. I will open a TAC Case. Thanks for your help.
[Expert@mgmt:0]# ls -la /dev/null
crw-rw-rw- 1 admin root 1, 3 Nov 7 13:54 /dev/null
I assume a chmod 666 /dev/null in expert mode would resolve this?
Thank you! That solved the Problem. Dont know why this was changed but now the users work normally again.
You should double check /dev/null. Can you post a
ls -l /dev/null
IMHO a script deleted /dev/null and created a new one. /dev/null isn't a normal file. It has to be a character device...
I do agree, we need to check what caused this in the first place. Just redefining permissions is not a solution but a workaround.
I found the Script which deleted the /dev/null. The Script had a syntax error. After that i recreated the /dev/null as character Device and rebooted the Management Server. Since there it looks stable and did not happen again.
Thank you all
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 29 | |
| 15 | |
| 6 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 |
Wed 10 Jun 2026 @ 01:00 PM (EDT)
Deep Dive: When the Agents Attack: A Live Look at Agentic Exposure ValidationThu 11 Jun 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #8: Say Yes to AI Without Saying Yes to RiskFri 12 Jun 2026 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 47: Continuous Threat Exposure ManagementTue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningWed 10 Jun 2026 @ 01:00 PM (EDT)
Deep Dive: When the Agents Attack: A Live Look at Agentic Exposure ValidationThu 11 Jun 2026 @ 11:00 AM (EDT)
Tips and Tricks 2026 #8: Say Yes to AI Without Saying Yes to RiskFri 12 Jun 2026 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 47: Continuous Threat Exposure ManagementTue 16 Jun 2026 @ 05:00 PM (CEST)
Under the Hood: Check Point SASE | Internet Access Optimization & Performance TuningThu 18 Jun 2026 @ 10:00 AM (CEST)
The Cloud Architects Series: Check Point WAF - The Next Generation of AI powered protectionAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY