Spoofing of UDDI/ebXML Messages
|Attack Pattern ID: 218 (Detailed Attack Pattern Completeness: Stub)||Typical Severity: Medium||Status: Draft|
An attacker spoofs a UDDI, ebXML, or similar message in order to impersonate a service provider in an e-business transaction. UDDI, ebXML, and similar standards are used to identify businesses in e-business transactions. Among other things, they identify a particular participant, WSDL information for SOAP transactions, and supported communication protocols, including security protocols. By spoofing one of these messages an attacker could impersonate a legitimate business in a transaction or could manipulate the protocols used between a client and business. This could result in disclosure of sensitive information, loss of message integrity, or even financial fraud.
The targeted business's UDDI or ebXML information must be served from a location that the attacker can spoof or compromise or the attacker must be able to intercept and modify unsecured UDDI/ebXML messages in transit.
The attacker must be able to force the target user to accept their spoofed UDDI or ebXML message as opposed to the a message associated with a legitimate company. Depending on the follow-on for the attack, the attacker may also need to serve its own web services.
Implementation: Clients should only trust UDDI, ebXML, or similar messages that are verifiably signed by a trusted party.
|CWE-ID||Weakness Name||Weakness Relationship Type|
|345||Insufficient Verification of Data Authenticity||Targeted|
|Nature||Type||ID||Name||Description||View(s) this relationship pertains to|
|ChildOf||Attack Pattern||148||Content Spoofing|
Mechanism of Attack (primary)1000