A vulnerability which could allow for DNS poisoning attacks has been discovered in the C standard libraries uClibe and uClibe-ng, which are widely used in IoT products. DNS poisoning enables a subsequent Man-in-the-Middle scenario, which can be used to perform actions like stealing information, forcing authenticated responses, as well as installing malicious firmware.
There is currently no CVE listing, nor further details on affected products, as the research group Nozomi Networks is still working with vendors and library developers in finding a solution.
The MS-ISAC believes that due to various mitigating factors, this vulnerability does not pose an immediate threat to our member base. We would, however, like to share relevant details for your situational awareness.
We find out why calls to Dublin airport’s noise complaints line have soared, and Carole quizzes Graham to celebrate World Password Day.
All this and more is discussed in the latest edition of the award-winning “Smashing Security” podcast, with computer security veterans Graham Cluley and Carole Theriault.
And don’t miss our special featured interview with Clint Dovholuk of NetFoundry.
Two vulnerabilities were discovered in the vhost code of DPDK, a set of
libraries for fast packet processing, which could result in denial of
service or the execution of arbitrary code.
Multiple vulnerabilities have been discovered in Mozilla Firefox and Firefox Extended Support Release (ESR), the most severe of which could allow for arbitrary code execution.
Mozilla Firefox is a web browser used to access the Internet.
Mozilla Firefox ESR is a version of the web browser intended to be deployed in large organizations.
Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution. Depending on the privileges associated with the user an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.
Agility and flexibility were key directives in the development of new technology, which is why on-premise assets soon transitioned into virtual machines, which further transformed into compact and swift containers. Modern enterprise network environments are increasingly transforming to be cloud-based, where both applications and data storage are hosted in a cloud — and often multi-cloud — environment. The attack surfaces and security protection requirements of software in distributed cloud environments are vastly different from traditional network architectures where applications and data were hosted on enterprise-owned servers in on-premises data centers.
Whether a company utilizes a private, hybrid or public cloud infrastructure or offers cloud services to others, it is critical that each cloud instance and service be isolated to help minimize the risk of data compromise. In a traditional network, networking equipment and firewalls segment and isolate physical servers and other devices. However, to effectively isolate cloud instances, technologies like micro-segmentation are needed.
Micro-segmentation can help minimize damage caused by a compromised cloud asset. It can reduce the severity to a contained incident that can be remediated quickly versus an expansive data breach that spans multiple parts of the business, or numerous clients in a multi-tenant service. While proper implementation of micro-segmentation is vital, at a high-level view it can be summarized as a 5-step process.
