Bug #5907
closed
User story #6363: Secure agent/server communication
Any user can forge a fake report
Description
This is a vulnerability.
Any user can write to syslog.
Therefore, any user can create a fake report telling rudder there is a problem (or there is no problem).
Updated by François ARMAND almost 10 years ago
Some more context: on a node, any user can log things to syslog. So the idea is that a malicious, non privileged user could forge fake syslog logs as Rudder reports.
Updated by Benoît PECCATTE over 9 years ago
- Category set to System integration
- Target version set to Ideas (not version specific)
- Parent task set to #6363
Updated by François ARMAND over 7 years ago
- Private changed from No to Yes
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to First impressions of Rudder
- Priority set to 0
I'm setting it to "first impression" because given the category of rudder, it is expected, even without testing it, to have a secured message protocol between nodes and server.
Updated by Benoît PECCATTE over 7 years ago
- Effort required set to Large
- Priority changed from 0 to 78
Updated by Alexis Mousset almost 6 years ago
- Related to Architecture #14008: Replace syslog by an HTTPS based communication for reporting added
Updated by Alexis Mousset over 5 years ago
- Status changed from New to Rejected
- Priority changed from 78 to 92
Fixed by #14800 with report signature validation in 5.1.
We provide a system variable to disable syslog for reporting and fix this in 5.1.
Will only completely disappear once syslog support is completely removed, in a future Rudder version.
Updated by Alexis Mousset over 4 years ago
- Category changed from System integration to Security
- Priority changed from 92 to 94
Updated by Alexis Mousset over 1 year ago
- Private changed from Yes to No
- Priority changed from 94 to 0