How severe is GHSA-r37h-j483-cjjm?

No CVSS score has been assigned to GHSA-r37h-j483-cjjm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r37h-j483-cjjm?

GHSA-r37h-j483-cjjm affects the following packages: phanan/koel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-r37h-j483-cjjm?

Update phanan/koel to 5.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r37h-j483-cjjm is resolved across your whole dependency graph.

How do I detect GHSA-r37h-j483-cjjm in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phanan/koel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r37h-j483-cjjm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-r37h-j483-cjjm?

O3 pinpoints whether GHSA-r37h-j483-cjjm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r37h-j483-cjjm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-r37h-j483-cjjm, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-r37h-j483-cjjm?

GHSA-r37h-j483-cjjm is classified as CWE-916 (CWE-916). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r37h-j483-cjjm published, and has it been updated?

GHSA-r37h-j483-cjjm was published on June 1, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-r37h-j483-cjjm

Improper rate limiting in Koel

Also known asCVE-2021-33563

Published

Jun 1, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐘phanan/koel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Koel before 5.1.4 lacks login throttling, lacks a password strength policy, and shows whether a failed login attempt had a valid username. This might make brute-force attacks easier.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phanan/koel`	all versions	5.1.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Koel before 5.1.4 lacks login throttling, lacks a password strength poli…

huntr.devNVDJun 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phanan/koel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phanan/koel to 5.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r37h-j483-cjjm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-r37h-j483-cjjm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r37h-j483-cjjm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Koel before 5.1.4 lacks login throttling, lacks a password strength policy, and shows whether a failed login attempt had a valid username. This might make brute-force attacks easier.

O3 Security · Impact-Aware SCA

Is GHSA-r37h-j483-cjjm in your dependencies?

O3 detects GHSA-r37h-j483-cjjm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works