Transporting bearer tokens from OAuth authorization flows as cleartext allowed
Issue ID: v3-global-securityscheme-http-bearer-clear
Average severity: Minimal
Description
One or more global security schemes in the API allows to set security requirements that accept bearer tokens from OAuth 2.0 authorization flows sent in cleartext over an unencrypted channel. Attackers can easily intercept API calls and retrieve the unencrypted tokens. They can then use the tokens to make other API calls.
This is a potential risk, because the definition is in security schemes. However, it easily turns into an actual risk when the unsafe method is used in a security requirement.
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:
{
"servers": [
{
"url": "http://my.api.server.com/",
"description": "API server"
}
],
// ...
"components": {
"securitySchemes": {
"bearerAuth": {
"type": "http",
"scheme": "bearer"
}
}
}
}
Possible exploit scenario
Attackers can intercept the access tokens simply by listening to the network traffic in a public WiFi network. They could also use a traffic logging tool on a smartphone, computer, or browser, or sniff the traffic in the network to get the tokens.
Remediation
Set all server
objects to support HTTPS only so that all traffic is encrypted.
{
"servers": [
{
"url": "https://my.api.server.com/",
"description": "API server"
}
],
// ...
"components": {
"securitySchemes": {
"bearerAuth": {
"type": "http",
"scheme": "bearer"
}
}
}
}