Anybody want to talk about Dirty Cow? Post: 302984395

Sponsored Content

The Lounge What is on Your Mind? Anybody want to talk about Dirty Cow? Post 302984395 by hicksd8 on Tuesday 25th of October 2016 11:57:18 AM

10-25-2016

Moderator

Here's a news clip from the UK. (BBC Copyright acknowledged)

Users of the Linux operating system are being urged to update it to remove a "serious" bug that hackers could use to hijack systems.
Known as the Dirty Cow bug, the vulnerability has been present in many versions of Linux for almost a decade.
The warnings come as malicious hackers start exploiting it to take over vulnerable computers.
The vulnerability gets its name from the Linux sub-system, called Copy-On-Write or COW, in which it appears.
Updated versions of Linux that no longer suffer the bug are now being widely distributed. Millions of computers, including a majority of web servers, run Linux or one of its variants.

"The nature of the vulnerability lends itself to extremely reliable exploitation," Dan Rosenberg, a security researcher at Azimuth Security, told tech news site Ars Technica. He added that it was the "most serious" bug of its type ever found in Linux.
The vulnerability allows attackers to steadily increase the amount of control they can exert over a target system.
Security expert Graham Cluley said the bug was of a type that did not normally prompt action because they were less likely to be exploited. However, he said, Dirty Cow should be taken seriously because there was some evidence that it was being actively abused.
Attack code that capitalised on the weakly protected sub-system was captured by developer Phil Oester as it was used in an attempt to take over a server he runs.
Mr Oester told the V3 tech news site that the vulnerability was easy to use and was "almost certain" to be more widely used by cyberthieves.

hicksd8

View Public Profile for hicksd8

Find all posts by hicksd8

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Quick-and-dirty g++ compilation

I am creating a small bash file that will take one argument and compile it: #!/bin/bash OUT=${$1%.cpp} # C++ source files always end in .cpp g++ -Wall $1 -o $OUT chmod 777 $OUT The error message says 'bad substitution', namely where OUT is defined. How to fix this?

2. AIX

Can't mount showing 0506-342 The superblock on /dev/fslv00 is dirty

Dear All Last day in Aix 5.2 server by executing # df –g I found following: Filesystem GB blocks Free %Used Iused %Iused Mounted on . . /dev/fslv00 58.00 136.70 -135% 212103 1% /sprod After shutting down by following command # shutdown –h And when...

3. UNIX for Advanced & Expert Users

Finding volumes with mirrored DRL(Dirty Region Log)

hi, How do I find VxVM volumes which have a mirrored DRL. thanks in advance Prasi

4. Shell Programming and Scripting

noob question - is awk the tool to clean dirty text files?

Hi, nevermind. I think I've found the answer. It appears I was looking for index, match, sub, and gsub. I want to write a shell script that will clean the html out of a bunch of files and format the data for import into excel. Awk seems like a powerful tool, but it seems oriented to...

5. Shell Programming and Scripting

Need a quick and dirty solution

I have a list of multiple versions of software. The list is formated as follows: NAME VERSION I simply need to pull out the highest version of each software, for example: Original File a v1.0 a v1.1 a v1.2 b v2.1 b v2.2 b v2.21 b v3.0 Output a v1.2 b v3.0

6. UNIX for Advanced & Expert Users

Superblock marked dirty

Good morning! I met a problem on a FS with AIX 5.3 It's not possible to mount the FS because of a dirty superblock. I tried few things without success. I need your help to solve my problem guys. Do you have any idea please? Thanks a lot drp01,/home/root # mount /GSPRES/data Replaying...

7. Linux

Broadcom under Fedora 18 (Spherical Cow)

So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module $uname Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux lspci -v 05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g...

LEARN ABOUT LINUX

ubuntu-bug

apport-bug(1)						      General Commands Manual						     apport-bug(1)

NAME

       apport-bug, apport-collect - file a bug report using Apport, or update an existing report

SYNOPSIS

       apport-bug

       apport-bug symptom | pid | package | program path | .apport/.crash file

       apport-collect report-number

DESCRIPTION

       apport-bug  reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys-
       tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds.

       You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most
       useful bug reports.

       If  there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program
       name to apport-bug, e. g.:

	   apport-bug firefox
	   apport-bug /usr/bin/unzip

       In order to add more information to the bug report that could help the developers to fix the problem, you can also  specify  a  process	ID
       instead:

	   $ pidof gnome-terminal
	   5139
	   $ apport-bug 5139

       As  a  special  case,  to  report  a  bug  against  the	Linux  kernel,	you  do  not  need  to	use  the full package name (such as linux-
       image-2.6.28-4-generic); you can just use

	   apport-bug linux

       to report a bug against the currently running kernel.

       Finally, you can use this program to report a previously stored crash or bug report:

	   apport-bug /var/crash/_bin_bash.1000.crash
	   apport-bug /tmp/apport.firefox.332G9t.apport

       Bug reports can be written to a file by using the --save option	or by using apport-cli.

       apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the  session
       does not run under X11, it calls apport-cli for a command-line client.

UPDATING EXISTING REPORTS

       apport-collect  collects  the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful
       if the report was not originally filed through Apport, and the developers ask you to attach information from your system.

OPTIONS

       Please see the apport-cli(1) manpage for possible options.

ENVIRONMENT

       APPORT_IGNORE_OBSOLETE_PACKAGES
	      Apport refuses to create bug reports if the package or any dependency is not current. If this  environment  variable  is	set,  this
	      check  is  waived.  Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or
	      temporarily on the command line when calling apport-bug.

SEE ALSO

       apport-cli(1)

AUTHOR

       apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.

Martin Pitt							September 08, 2009						     apport-bug(1)