SAP R/3 Remote Function Call API Lets Remote Users Conduct Password Guessing Attempts
|
|
SecurityTracker Alert ID: 1006223 |
|
SecurityTracker URL: http://securitytracker.com/id/1006223
|
|
CVE Reference:
CVE-2003-1035
(Links to External Site)
|
Updated: Mar 16 2004
|
Original Entry Date: Mar 5 2003
|
Impact:
Host/resource access via network
|
Exploit Included: Yes
|
Version(s): SAP R/3 4.6C/D
|
Description:
A vulnerability was reported in SAP R/3. A remote user can conduct unlimited login attempts using the SAP Remote Function Call (RFC) API without being subject to account lockouts.
It is reported that the SAP R/3 GUI will lock out the remote user after a certain number of invalid login attempts. However, the RFC API reportedly does not implement lockouts.
A remote user can conduct continuous password guessing attempts.
|
Impact:
A remote user can conduct password guessing attempts without being locked out.
|
Solution:
No solution was available at the time of this entry.
|
Vendor URL: www.sap.com/ (Links to External Site)
|
Cause:
State error
|
Underlying OS: Linux (Any), UNIX (AIX), UNIX (HP/UX), UNIX (Solaris - SunOS), UNIX (Tru64), Windows (NT), Windows (2000)
|
Underlying OS Comments: Confirmed on Windows 2000
|
|
Message History:
None.
|
Source Message Contents
|
Subject: [Full-Disclosure] SAP R/3, account locking and RFC SDK
|
--=-dzYhkVGc1hCmMD6j/+rh
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi,
I wrote a networked password checker for SAP R/3, mainly based on the
sapinfo program provided by SAP and using the RFC (Remote Function Call)
API.
In a default install of SAP R/3, three bad login/password attempts in
the SAPGUI will kill the GUI. After 4 SAPGUI deaths (4*3 =3D 12 attempts),
the tested account is locked (UFLAG=3D128 in SAPR3.USR02).
My problem is that, with the RFC API, I can check as much login/password
combo as I want, without locking the target account. Once the password
is found, I just have to use SAPGUI to log in the SAP system.
So, IMO and as far as I tested it, account locking isn't working via the
API provided by the SDK RFC. Could somebody confirm this behaviour ?
This was tested on Linux for the client side and on Win2K for the server
side. The release of SAP R/3 is 46C/D.
Regards,
--=20
Nicolas Gregoire ----- Consultant en S=E9curit=E9 des Syst=E8mes d'Informat=
ion
ngregoire@exaprobe.com ------[ ExaProbe ]------ http://www.exaprobe.com/
PGP KeyID:CA61B44F FingerPrint:1CC647FF1A55664BA2D2AFDACA6A21DACA61B44F
--=-dzYhkVGc1hCmMD6j/+rh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQA+ZMxGuhlqje80vsMRAi56AKCuSkw1LDaIKHpsRoVYHlZaD7mnOQCeOd6q
nDW5YBQ7IpRfSLn4Dz7PxFw=
=CFQa
-----END PGP SIGNATURE-----
--=-dzYhkVGc1hCmMD6j/+rh--
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
|
|
