SeaCat Application Security Technology Is Not Impacted by the Dirty Cow Issue (CVE-2016-5195)
Tuesday, October 25, 2016
The new vulnerability, DirtyCOW, (CVE-2016-5195) exploits a flaw in private read-only memory mappings. However, this critical impact vulnerability has existed in Linux for nine years and only got discovered recently.
DirtyCOW allows applications and users to elevate user rights and gain unlimited access to the operating system. Millions of Linux installations are vulnerable including many Android phones because Android was built on Linux.
This vulnerability is caused by a breakage of read-only memory mapping in a copy-on-write (COW) process. Although DirtyCOW can only be exploited locally, the risk is very high because there are many available working exploits on the Internet.
The fix for this vulnerability only makes a small change in the copy-on-write processing, and already available for all the main Linux distributions.
If you are sure that you uses only approved applications installed on the server, and no other user has access to this server, you are probably not susceptible to data loss. Otherwise, your data can be lost or stolen. Please be aware that your system log does not register a successful exploitation of the DirtyCow.
In all cases, it's extremely importantly to apply the patch. If you'd like assistance or have any question please contact firstname.lastname@example.org. Alternatively, look at our documentation to know more about SeaCat application security.
You Might Be Interested in Reading These Articles
We help you to operate your mobile and IoT apps securely. You may have noticed that OpenSSL released a new version on 26 January 2017. The new release fixed one low-severity issue and three moderate ones.
Published on January 26, 2017
OpenSSL DROWN Vulnerability Affects Millions of HTTPS Websites and Software Supporting SSLv2 (CVE-2016-0800)
DROWN is caused by legacy OpenSSL SSLv2 protocol, known to have many deficiencies. Security experts have recommended to turn it off, but apparently many servers still support it because disabling SSLv2 requires non-default reconfiguration of the SSL cryptographic settings which is not easy for common IT people who have limited security knowledge and don’t know the location to disable this protocol and the way to disable it.
Published on April 12, 2016
We help you to operate your mobile app(s) securely. You might have noticed that OpenSSL has recently announced an emergency release because they identified a series of security defects, rated with maximum severity High. The version of fixed OpenSSL is 1.0.2h, released on 3rd May 2016.
Published on May 04, 2016