CAPEC-51
Poison Web Service Registry
2014-06-23
00h00 +00:00
00h00 +00:00
Cảnh báo cho một CAPEC
Luôn được thông báo về mọi thay đổi đối với một CAPEC cụ thể.
Mô tả CAPEC
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.
Thông tin CAPEC
Luồng thực thi
1) Explore
[Find a target SOA or Web Service] The adversary must first indentify a target SOA or Web Service.
2) Experiment
[Determine desired outcome] Because poisoning a web service registry can have different outcomes, the adversary must decide how they wish to effect the webservice.
Kỹ thuật
- An adversary can perform a denial of service attack on a web service.
- An adversary can redirect requests or responses to a malicious service.
3) Experiment
[Determine if a malicious service needs to be created] If the adversary wishes to redirect requests or responses, they will need to create a malicious service to redirect to.
Kỹ thuật
- Create a service to that requests are sent to in addition to the legitimate service and simply record the requests.
- Create a service that will give malicious responses to a service provider.
- Act as a malicious service provider and respond to requests in an arbitrary way.
4) Exploit
[Poison Web Service Registry] Based on the desired outcome, poison the web service registry. This is done by altering the data at rest in the registry or uploading malicious content by spoofing a service provider.
Kỹ thuật
- Intercept and change WS-Adressing headers to route to a malicious service or service provider.
- Provide incorrect information in schema or metadata to cause a denial of service.
- Delete information about service procider interfaces to cause a denial of service.
Điều kiện tiên quyết
The attacker must be able to write to resources or redirect access to the service registry.Kỹ năng cần thiết
To identify and execute against an over-privileged system interfaceTài nguyên cần thiết
Capability to directly or indirectly modify registry resourcesCác biện pháp giảm thiểu
Design: Enforce principle of least privilegeDesign: Harden registry server and file access permissions
Implementation: Implement communications to and from the registry using secure protocols
Điểm yếu liên quan
| Tên điểm yếu | |
|---|---|
CWE-285 |
Improper Authorization The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
CWE-74 |
Improper Neutralization of Special Elements in Output Used by a Downstream Component The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
CWE-693 |
Protection Mechanism Failure The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. |
Gửi
| Tên | Tổ chức | Ngày | Ngày phát hành |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation |
Sửa đổi
| Tên | Tổ chức | Ngày | Bình luận |
|---|---|---|---|
| CAPEC Content Team | The MITRE Corporation | Updated Description, Execution_Flow | |
| CAPEC Content Team | The MITRE Corporation | Updated Description, Extended_Description | |
| CAPEC Content Team | The MITRE Corporation | Updated Example_Instances |
