Typical severity: Very High. Likelihood of attack: High. SOA and Web Services often use a registry to perform look up, get schema information, and metadata about services. A poisoned registry can redirect (think phishing for servers) the service requester to a malicious service provider, provide incorrect information in schema or metadata, and delete information about service provider interfaces.
Design: Enforce principle of least privilege | Design: Harden registry server and file access permissions | Implementation: Implement communications to and from the registry using secure protocols