Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31597PUBLISHED: 2021-04-23The xmlhttprequest-ssl package before 1.6.1 for Node.js disables SSL certificate validation by default, because rejectUnauthorized (when the property exists but is undefined) is considered to be false within the https.request function of Node.js. In other words, no certificate is ever rejected.
CVE-2021-2296PUBLISHED: 2021-04-22
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). The supported version that is affected is Prior to 6.1.20. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromi...
CVE-2021-2297PUBLISHED: 2021-04-22
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). The supported version that is affected is Prior to 6.1.20. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromi...
CVE-2021-2298PUBLISHED: 2021-04-22
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.23 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attac...
CVE-2021-2299PUBLISHED: 2021-04-22
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.23 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful atta...
0 Comments
Tweet This
User Rank: Apprentice
1/18/2013 | 2:35:02 PM
when you conduct an application security assessment, whether itGÇÖs a static
analysis scan, dynamic analysis scan, penetration test, or code review, you are
going to be presented with a set of vulnerabilities to fix. Often times, there
are more vulnerabilities to be fixed than time to fix them, so how do you
determine which you should address?
I believe the answer is a vulnerability
classification and a prioritization framework. Once you have these in place,
you will have good framework for classifying and responding to discovered
vulnerabilities. If you want to read more about software vulnerability management,
hereGÇÖs a great article I think you might find interesting: http://blog.securityinnovation....
Keep up the good work!