Denial of Service (DoS) Affecting github.com/ory/oathkeeper/pipeline/authn package, versions >=0.38.0-beta.2 <0.38.12-beta.1
Do your applications use this vulnerable package?
23 Jun 2021
23 Jun 2021
How to fix?
github.com/ory/oathkeeper/pipeline/authn to version 0.38.12-beta.1 or higher.
Affected versions of this package are vulnerable to Denial of Service (DoS). When making a request to an endpoint that requires the scope
foo using an access token granted with that
foo scope, introspection will be valid and that token will be cached. The problem comes when a second request to an endpoint that requires the scope
bar is made before the cache has expired. Whether the token is granted or not to the
bar scope, introspection will be valid.
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm