So, why am I disgruntled? My company recently signed on for RSI's
Member Services. This entitled us to some "unreleased" security
information that had been submitted to vendors and members only.
One advisory in particular dealt with a HUGE problem in libnsl on
various Sun platforms. Subsequently, when we took a look at our own
systems and we realized that our entire network had been owned via this
vulnerability, backdoored, you name it - we were fucked. It's taken a
lot of time to get us back to the point where I can run the networks and
stop worrying about all these security problems that should have been
patched long ago.
I don't fault RSI for this - I'm happy they made us aware of these
problems so long ago. It's just too bad Sun has chosen to ignore them.
I find it absolutely PATHETIC that a company of Sun's size and
resources, who has had the fucking information for almost 2 months,
cannot produce a patch more quickly for a problem of this magnitude.
So, despite my companies agreement with RSI, I am releasing the
information anonymously. Oh, did I forget to tell you that this is not
the only problem Sun is sitting on? I'm hoping with this public
disclosure it will force Sun to throw more resources at the problem(s).
Assholes.
Extremely Disgruntled Sun Admin.
RSI.0003.05-14-98.SUN.LIBNSL
|:::. |::::: |::::. |::::: |::::: |::::.
.. :: .. .. :: .. .. .. ::
|:::: |:::: |:::: :::::: |::::: |:::: |:
|: :: |: |: |:: |: |: ::
|: :: |::::: |: |::::: |::::: |:::::
Repent Security Incorporated, RSI
[ http://www.repsec.com ]
*** RSI ALERT ADVISORY ***
--- [CREDIT] -------------------------------------------------------
Matt Conover: Discovered the vulnerabilities
Mark Zielinski: Author of advisory
---[SUMMARY]--------------------------------------------------------
Announced: May 14, 1998
Report code: RSI.0003.05-14-98.SUN.LIBNSL
Report title: Sun Microsystem's libnsl
Vulnerability: Insufficient bounds checking
Vendor status: Contacted, patch supplied
Patch status: Awaiting patch from Sun Microsystem's
Platforms: Solaris 2.2, 2.3, 2.4, 2.5.1
Vulnerable: Several library functions in libnsl have buffer
overflows
Reference: http://www.repsec.com/advisories.html
Impact: If exploited, an attacker could potentially compromise
both local and remote root access on your server
--- [DETAILS] --------------------------------------------------------
Problem: Several buffer overflows exist in Sun Microsystem's
libnslnetworking library.
While overwriting the buffer, the attacker can
manipulate the stack and execute their own commands,
possibly gaining root access on your server.
Functions we have found vulnerable:
Vulnerable key functions
---------------------------------------------------
extract_secret () : Buffer overflows while
copyingdata into a local
buffer
getkeys_nis () : Buffer overflows if key value
is larger then the buffer
getpublickey () : Calls getkeys_nis ()
getsecretkey () : Calls getkeys_nis ()
Vulnerable RPC functions
----------------------------------------------------
authdes_seccreate () : Calls getpublickey ()
rpc_broadcast_exp () : Buffer overflow if allowed to
specify network protocol type
rpc_broadcast () : Calls rpc_broadcast_exp ()
clnt_create_timed () : Buffer overflow if allowed to
specify network protocol type
host2netname () : Buffer overflow while
specifying hostname.
getnetname () : Calls host2netname ()
clnt_create () : Calls clnt_create_timed ()
rpc_call () : Buffer overflow if allowed to
specify network protocol type
authdes_pk_seccreate () : Calls getnetname ()
Vulnerable NIS functions
----------------------------------------------------
__nis_init_callback () : Calls getpublickey ()
__nis_core_lookup () : Buffer overflow while copying
paramaters into a local
buffer
nis_make_rpchandle () : Calls host2netname ()
nis_dump_r () : Calls nis_make_rpchandle ()
nis_dump () : Calls nis_dump_r ()
__nis_auth2princ () : Buffer overflow while
specifying machine name
__nis_host2nis_server (): Buffer overflow while
specifyinghostname
nis_name_of_r () : Buffer overflow while copying
paramaters into a local
buffer
nis_old_data_r () : Buffer overflow while copying
paramaters into a local
buffer
nis_list () : Calls __nis_core_lookup ()
nis_add () : Calls nis_nameops ()
nis_remove () : Calls nis_nameops ()
nis_modify () : Calls nis_nameops ()
nis_mkdir () : Calls nis_make_rpchandle ()
nis_rmdir () : Calls nis_make_rpchandle ()
Potentially vulnerable programs
----------------------------------------------------
Calls vulnerable RPC functions:
1. nfs mount
2. nfs share
3. rpc.rexd
4. autofs
Calls vulnerable key functions:
1. chkey
2. keylogin
3. setkey
4. newkey
5. keyserv
6. libscheme
Calls vulnerable NIS functions:
1. rpc.nisd
2. rpc.nisdpasswdd
3. nisping
4. nisaddent
5. nisupdkeys
6. nisaddcred
7. sendmail
8. volcheck
9. vold
Calls vulnerable YP functions:
1. vacation
2. ypwhich
3. yppush
These vulnerabilities are present in Sun Microsystem's
Solaris 2.2, 2.3, 2.4 and 2.5.1.
For more information on this type of attack, point your
web browsers to http://www.repsec.com/bofs.html.
--- [FIX] ------------------------------------------------------------
Solution: Refer to the PATCH section.
--- [PATCH] ----------------------------------------------------------
Solution: Wait until Sun Microsystem's can release a official
patch.
----------------------------------------------------------------------
Snail Mail:
Repent Security Incorporated (RSI)
adviseat_private
13610 N. Scottsdale Rd.
Suite #10-326
Scottsdale, AZ
85254
[ http://www.repsec.com ]
----------------------------------------------------------------------
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNAzU6dqAAAAEEAOHt9a5vevjD8ZjsEmncEbFp2U7aeqvPTcF/8FJMilgOVp75
dshXvZixHsYU7flgCNzA7wLIQPWBQBrweLG6dx9gE9e5Ca6yAJxZg8wNsi06tZfP
nvmvf6F/7xoWS5Ei4k3YKuzscxlyePNNKws6uUe2ZmwVoB+i3HHT44dOafMhAAUT
tBpSZXBTZWMgPGFkdmlzZUByZXBzZWMuY29tPg==
=ro8H
-----END PGP PUBLIC KEY BLOCK-----
Copyright May 1998 RepSec, Inc.
The information in this document is provided as a service to customers
of RepSec, Inc. Neither RepSec, Inc., nor any of it's employees, makes
any warranty, express or implied, or assumes any legal liability or
responsibility for the accuracy, completeness, or usefulness of any
information, apparatus, product, or process contained herein, or
represents that its use would not infringe any privately owned rights.
Reference herein to any specific commercial products, process, or
services by trade name, trademark, manufacturer, or otherwise, does not
necessarily constitute or imply its endorsement, recommendation or
favoring by RepSec, Inc. The views and opinions of authors express
herein do no necessarily state or reflect those of RepSec, Inc., and may
not be used for advertising or product endorsement purposes.
RSI Member Alert Advisories are expressly prohibited from release of any
and all information contained in this advisory, in any and all forms
into the public domain by RepSec Members, their personnel, or other
related or affiliated personnel, to other advisory groups and/or other
security incident response teams (both commercial and non-commercial) -
during the period RSI Member Alert Advisories are released to RSI
Member's only. The material in this advisory alert may be reproduced
and distributed, without permission, only after it has been released by
RepSec, Inc. into the public domain. After release by RepSec, Inc. into
the public domain the material in this RSI Member Alert Advisory may be
reproduced and distributed, without permission in its entirety only,
provided the copyright is kept intact and due credit is given to RepSec,
Inc.
Subject to the timing of release restrictions above, this RSI Advisory
Alert may be reproduced and distributed, without permission, in its
entirety only, by any person provided such reproduction and/or
distribution is performed for non-commercial purposes and with the
intent of increasing the awareness of the Internet community.
----------------------------------------------------------------------
RepSec, Inc. are trademarks of RepSec, Inc. All other trademarks are
property of their respective holders.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:01:30 PDT