Features
- Online Dictionary Attack
- Presence Stealing
- Contact List Stealing
- Single User Flood Mode (Internal)
- Domain Flood Mode (Internal)
- Call Walk (Internal/External)
- Play Spam Audio
- Detailed Report Generation
Authors

Dictionary Attack
OAT tests the password strength of Microsoft Office Communication users. In online password breaking mode, OAT attempts to authenticate as a legitimate user. This mode imitates a real outside attack and thus serves as a valuable security auditing tool.
Presence Stealing
The "Presence Stealing" feature forms the basis of every attack module present in OAT. Once OAT fetches the contact list ( External Network) or SIP enabled users from the Domain Controller (Internal network), it tries to determine their presence status by sending special SERVICE requests to the OCS Server. Subscribing for Presence was not officially supported in UCMA SDK until version 2.0. OAT uses a SOAP-XML message body ( not officially supported by Microsoft) to "steal" the presence information.
This presence information is used for launching additional UC attacks against the target users. OFFLINE SIP users are not targeted by OAT in supported attacks.
Contact List Stealing
This feature is used from an External Network attack scenario. Once OAT successfully breaks the password of target user, it first registers itself as the target user. OAT then subcribes for the roaming contacts of the target users and elicits their presence status.
OAT also tries to subscribe for itself as well as trying to determine if someone else has subscribed for the target users. The objective behind subscribing itself is enumeration of the maximum target SIP users for launching attacks from outside of the perimeter IP network.
Internal Attack Modes
- When launched from the Internal network, OAT can be used to flood in the two following modes. These features can be accessed from the third tab of the OAT user interface.
Both of these modes are supported only in internal network attack.
As the name suggests, this mode is used to flood only a single target user from the network. When selected, the attacker is required to enter the SIP URI of target user in the provided text box.
When the attack begins, OAT uses its Presence Stealing feature module and attempts to get presence status of target user. If the target is not offline, OAT will flood the user with 'n' number of IM messages. Number of spam messages can be specified before starting attack.
This mode is completely different and has a higher service impact, as it floods all online user present in the domain. When launched from internal network, OAT attempts to fetch all SIP communication enabled users from the domain controller. This gives access to all users using OCS communicator within the enterprise network. After OAT elicits the required target base, it determines their presence and floods these users with SPAM messages.
OAT does not flood Offline users because sending Offline IM messages is not supported by OCS server.
Call Walking is the process of calling every user in the network. In internal callwalking mode, OAT first fetches all of the SIP enabled users from the domain controller. Armed with their presence information, the attacker can run the call walking exploit. In this attack, OAT places a call to every online user.
External Attack Modes
-
External attack is a more realistic attack mode and simulates a real world attack scenario. After successfully breaking target user's password sourced from the external IP network,
OAT steals the contact list of the targeted user, and uses the contact list to build a target victim list.
The attacker can then choose between the following attack modes from the External Network.
All above external attack modules are similar to the one mentioned above in Internal Attack modules. The key difference is that OAT is limited in reconnaisance of victim users from the external network.
Report Generation
OAT has a report generation capability in every attack module. The attacker needs to check the check box if they want OAT to generate a report. Reports will contains all steps performed by OAT in the attack process.
These reports can be viewed in the second last tab of OAT user interface. Attacker can save the selected report in Text format.

