Rule

--
Sid
24628

--
Summary:
This event is generated when an attempt is made to exploit a known vulnerability in webmin.

--
Impact:
Denial of Service. Information disclosure. Loss of integrity. 

--
Detailed Information:
file/show.cgi in Webmin 1.590 and earlier allows remote authenticated users to execute arbitrary commands via an invalid character in a pathname, as demonstrated by a | (pipe) character.

--
Affected Systems:
gentoo webmin 1.140
gentoo webmin 1.150
gentoo webmin 1.160
gentoo webmin 1.170
gentoo webmin 1.180
gentoo webmin 1.200
gentoo webmin 1.210
gentoo webmin 1.220
gentoo webmin 1.230
gentoo webmin 1.240
gentoo webmin 1.260
gentoo webmin 1.270
gentoo webmin 1.280
gentoo webmin 1.290
gentoo webmin 1.300
gentoo webmin 1.310
gentoo webmin 1.320
gentoo webmin 1.330
gentoo webmin 1.340
gentoo webmin 1.370
gentoo webmin 1.380
gentoo webmin 1.390
gentoo webmin 1.400
gentoo webmin 1.410
gentoo webmin 1.420
gentoo webmin 1.430
gentoo webmin 1.440
gentoo webmin 1.450
gentoo webmin 1.470
gentoo webmin 1.480
gentoo webmin 1.500
gentoo webmin 1.510
gentoo webmin 1.520
gentoo webmin 1.530
gentoo webmin 1.550
gentoo webmin 1.560
gentoo webmin 1.570
gentoo webmin 1.580
gentoo webmin 1.590

--
Attack Scenarios:
Many types of buffer overflow exist, this is a generic term that may apply to many circumstances that result in an overflow of some kind. A parameter overflow for example, means that the attacker is able to supply data as a parameter to the execution of a program. When the program expands the supplied data, if the size of the parameter is not correctly checked, it may exceed a set limit allowing the attacker to overflow the buffer and write data into memory.
In a stack overflow, the attacker has the opportunity to overwrite a return memory address which allows them to point the return address to a memory location containing code they wish to execute. This allows the attacker to run code with the full privileges of the program in use. The attacker may also supply the address for a known important call, for example the system() call, with the arguments to the call on the stack. The stack also contains the stack pointer and the frame pointer, overwriting these values may lead to a write-what-where condition.
In a heap overflow, it is possible to overwrite function pointers that may be in memory. This may allow the attacker to execute code in memory by changing the function pointer to move to code of their choosing. This can occur even in programs that do not necessarily use function pointers since they may be left in memory at run time. The heap also contains user data which also becomes visible to the attacker.

--
Ease of Attack:
Medium.

--
False Positives:
None known.

--
False Negatives:
None known.

--
Corrective Action:
Upgrade to the latest non-affected version of the software.

Apply the appropriate vendor supplied patches.

--
Contributors:
Sourcefire Vulnerability Research Team
This document was generated from data supplied by the National Vulnerability Database. A product of the National Institute of Standards and Technology.
For more information see http://nvd.nist.gov/

--
Additional References:

NIST CVE-2012-2982:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-2982
 
Common Weakness Enumeration:
http://cwe.mitre.org/data/definitions/120.html
 
Common Attack Pattern Enumeration and Classification:
http://capec.mitre.org/data/definitions/100.html

--
