Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3317PUBLISHED: 2021-01-26KLog Server through 2.4.1 allows authenticated command injection. async.php calls shell_exec() on the original value of the source parameter.
CVE-2013-2512PUBLISHED: 2021-01-26The ftpd gem 0.2.1 for Ruby allows remote attackers to execute arbitrary OS commands via shell metacharacters in a LIST or NLST command argument within FTP protocol traffic.
CVE-2021-3165PUBLISHED: 2021-01-26SmartAgent 3.1.0 allows a ViewOnly attacker to create a SuperUser account via the /#/CampaignManager/users URI.
CVE-2021-1070PUBLISHED: 2021-01-26
NVIDIA Jetson AGX Xavier Series, Jetson Xavier NX, TX1, TX2, Nano and Nano 2GB, L4T versions prior to 32.5, contains a vulnerability in the apply_binaries.sh script used to install NVIDIA components into the root file system image, in which improper access control is applied, which may lead to an un...
CVE-2021-1071PUBLISHED: 2021-01-26
NVIDIA Tegra kernel in Jetson AGX Xavier Series, Jetson Xavier NX, TX1, TX2, Nano and Nano 2GB, all L4T versions prior to r32.5, contains a vulnerability in the INA3221 driver in which improper access control may lead to unauthorized users gaining access to system power usage data, which may lead to...
User Rank: Apprentice
8/28/2012 | 2:03:26 AM
All throughout history, there have been things going on that the average Joe or Jane on the street don't know about but should be thankful for - things that their country is doing to protect them, whether they approve or disapprove of it.
Kaspersky's a funny guy here - sure, go ahead, ban malware. Doesn't that put him out of business? And as other posters have mentioned, sure, you can have every country on the face of the planet sign a treaty saying that they won't develop or use malware - but that doesn't keep a 14 year old kid from sitting down and learning assembly, C, or any other language and building something that could obliterate a network. No, a treaty, while nice on paper... exists only on paper.
Having malware banned leads to a false sense of security - sure, let's ban it... and forget how to defend against it. Then when the next attack happens, it's magnitudes worse. And the next attack will happen, it's just a matter of when. You have to be ready for it... and a treaty is not going to do much to help prevent an attack or clean up after one.
Andrew Hornback
InformationWeek Contributor