Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23381PUBLISHED: 2021-04-18This affects all versions of package killing. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23374PUBLISHED: 2021-04-18This affects all versions of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23375PUBLISHED: 2021-04-18This affects all versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23376PUBLISHED: 2021-04-18This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23377PUBLISHED: 2021-04-18This affects all versions of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
0 Comments
Tweet This
User Rank: Strategist
3/31/2016 | 3:40:03 PM
The key is to verify that the (daily) backups are clean, as a means of early ransomware detection and preventing good backups from being over-written. Nowhere do I see detailed advice on verifying backup integrity: a) How do you verify that a backup is not encrypted? Can it be automated or would it need a human to detect encrypted data? b) Keep in mind databases, Exchange, Active Directory and data in non-readable formats.
One solution to automating the integrity check is to seed your data with known static data- static files, database records, a mailbox, etc. Only the seed data could be restored and checked against the expected value. But this would be a custom solution, not something off the shelf as far as I know. In fact, seed data could be copied (low-level copy to bypass ransomware hooks into the OS) to another system and checked against expected values even hourly, as an early warning system for ransomware. Has anyone tried this approach?