Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-26814PUBLISHED: 2021-03-06
Wazuh API in Wazuh from 4.0.0 to 4.0.3 allows authenticated users to execute arbitrary code with administrative privileges via /manager/files URI. An authenticated user to the service may exploit incomplete input validation on the /manager/files API to inject arbitrary code within the API service sc...
CVE-2021-27581PUBLISHED: 2021-03-05The Blog module in Kentico CMS 5.5 R2 build 5.5.3996 allows SQL injection via the tagname parameter.
CVE-2021-28042PUBLISHED: 2021-03-05Deutsche Post Mailoptimizer 4.3 before 2020-11-09 allows Directory Traversal via a crafted ZIP archive to the Upload feature or the MO Connect component. This can lead to remote code execution.
CVE-2021-28041PUBLISHED: 2021-03-05ssh-agent in OpenSSH before 8.5 has a double free that may be relevant in a few less-common scenarios, such as unconstrained agent-socket access on a legacy operating system, or the forwarding of an agent to an attacker-controlled host.
CVE-2021-3377PUBLISHED: 2021-03-05The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.
User Rank: Ninja
7/26/2018 | 3:06:35 PM
→ Training needs to be put at the forftont, we need to evaluate the talent we have on staff on a consistent basis
→ Firewalls, routers, switches and other network gear needs to be follow the NSA security guidelines and framework - https://www.vmguru.com/2017/04/sizing-your-vmware-infrastructure/ (we need to add to this guideline and continue to test so we can push the envelope (or at least get close)
→ We really need to remove IPv4 from the mix of solutions and move to an IPv6 (pure) environment
→ We need to have a moc setup where we pay someone to hack the environment and we test the people there by putting them into a scenario
→ Application programming methodologies need to be reviewed by qualified hackers who have a deveopment background
→ We need to employ machine learning in the mix of products where the technology is always checking to see who is accessing what and reporting or even thwarting it
→ We need to automate the pentesting process but tailor it to our needs, get it to the point that the vulnerabilities can be mitigating by a autonomic programming change
→ We need to prioritize the threats or vulnerabilities, schedule weekend schedule patch and system updates to ensure the systems meet a certain severity level (sev1-5) and if the sev level is reviewed by outside vendor (reputable)
→ Implement next generation firewalls, endpoint monitoring, NMS, HIDS, NIDS, Zone/Layering and application integration without our existing security tools
→ We need a protocol monitoring device that identifies and baselines relationships between systems and applications, if there is an outside presence, then the system needs to tell us
→ Move pertinent data to zone 0, do not install DB on Web applications (separation of duties) and only allow data to write after a cleansing or holding area (similar to ACH) to ensure the data has not been compromised
→ If multiple records have been extracted by an outside source (Database), there needs to be a warning and action to go along with this potential threat, or at least after 10 records, then something needs to stop the data extraction (notification or autonomic stoppage)
→ If we are not doing business with a specific country, then block those countries that are not in our purvey using ACLs, NGFW with Country blocking capability
→ DNS needs to be configured with DNSSEC using specific keys that are stored in a safe place and only allow queries (recursive) to be done by systems that are internal, anything from the outside trying to access and perform lookups internally with outside IP addresses need to be thwarted
There are other things but this all I can think of right now.
Todd