Operation accepts HTTP requests in the clear

Issue ID: v3-operation-http-clear

Average severity: Medium

Description

The API operation accepts HTTP communications in the clear. HTTP traffic is not encrypted and can thus be easily intercepted.

For more details, see the OpenAPI Specification.

Example

The following is an example of how this type of risk could look in your API definition. The alternative server defined for the operation accepts unencrypted connections:

{
    "get": {
        "description": "Returns pets based on ID",
        "summary": "Find pets by ID",
        "operationId": "getPetsById",
        "servers": [
            {
                "url": "http://my.api.com",
                "description": "Development server"
            }

        ]
        // ...
    }
}

Possible exploit scenario

If your API supports unencrypted HTTP connections, all requests and responses are transmitted in the open. Anyone listening to the network traffic while the calls are being made may intercept them.

Remediation

Use only secure connections for the servers:

{
    "get": {
        "description": "Returns pets based on ID",
        "summary": "Find pets by ID",
        "operationId": "getPetsById",
        "servers": [
            {
                "url": "https://my.api.com",
                "description": "Development server"
            }

        ]
        // ...
    }
}