Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3493PUBLISHED: 2021-04-17
The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivile...
CVE-2021-3492PUBLISHED: 2021-04-17
Shiftfs, an out-of-tree stacking file system included in Ubuntu Linux kernels, did not properly handle faults occurring during copy_from_user() correctly. These could lead to either a double-free situation or memory not being freed at all. An attacker could use this to cause a denial of service (ker...
CVE-2020-2509PUBLISHED: 2021-04-17
A command injection vulnerability has been reported to affect QTS and QuTS hero. If exploited, this vulnerability allows attackers to execute arbitrary commands in a compromised application. We have already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later Q...
CVE-2020-36195PUBLISHED: 2021-04-17
An SQL injection vulnerability has been reported to affect QNAP NAS running Multimedia Console or the Media Streaming add-on. If exploited, the vulnerability allows remote attackers to obtain application information. QNAP has already fixed this vulnerability in the following versions of Multimedia C...
CVE-2021-29445PUBLISHED: 2021-04-16
jose-node-esm-runtime is an npm package which provides a number of cryptographic functions. In versions prior to 3.11.4 the AES_CBC_HMAC_SHA2 Algorithm (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDe...
0 Comments
Tweet This
User Rank: Ninja
6/9/2017 | 1:14:57 PM
A project requirement I see missing from many a project plan is exactly the things you are referring to, including milestones for data integrity checks before, during and after projects, whether they are one-off requests for an overnight tweak or a year-long project. Luckily for my team we work hand-in-hand with teams like Security and Compliance. We treat all requests the same, we care for the data in the same manner regardless the project. But the requirements should still be documented as many projects may overlook such "minutia".
Time to Market should not compromise integrity and all considerations related to Security and Compliance should be built into the day-to-day operations of every team member who has charge over sensitive data. And, the requirements for such data management written into project plans, no matter how small large, and the operational mind-set of every user with access well trained to avoid breaches of this type.