Unauthorized access to a Netease system causes Intranet penetration (continued)

Well, I want to use some testing machines of the reported vulnerabilities to see where they can penetrate. As a result, Netease has various internal systems, various servers, and various vulnerabilities ......
Detailed Description: Then the above: http://www.bkjia.com/Article/201208/151524.html for testing.
The information obtained from the cracked email address and internal forum is as follows:
1. SVN, Development Resource Platform, and corporation OA addresses, but can only be accessed from internal addresses.
2. user name and password of several test machines.
Objectives:
Log on to SVN, the technical department knowledge base, and the company's OA, and try to penetrate into it to see where it can penetrate.>. <

Test process:
Log on to 218.107.63.245 and check the NIC information. I found that an interface to the Intranet exists.




This test machine can directly access SVN




However, the Development Resource Platform and the OA system of the company are still inaccessible. So I searched for other useful information on the test machine, but did not find anything useful. Then install the scanner and scan the machines in the same network segment first. Because there is no firewall, there will be more information.
After scanning, no usable things are found. At this time, the penetration is back to the original location -- 218.107.63.245 on this test machine.
The Remote Desktop logon information contains the IP address range 192.168.130.0.




As a result, the scan results show that N machines are Windows XP systems, and 3389 and telnet are enabled. I guess the password is the same as 218.107.63.245. I tried telnet to test the password ~




Remote Desktop to 192.168.130.93, haoka 0.0
The test can access the Development Resource Platform and the corporation OA.

Technical Department Knowledge Base




Company office OA, the password should be another set, using the mailbox password can not log on.






Well, there are various systems in the Intranet. Some systems or servers have vulnerabilities. Check and fix them by yourself.
Penetration ends here.

Proof of vulnerability:
In the detailed description.

In addition to the test requirements, this penetration has nothing to do with the internal system.

Solution:
You should understand.