CVE-2024-54330
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedServer-Side Request Forgery (SSRF) vulnerability in hurraki Hurrakify hurrakify allows Server Side Request Forgery.This issue affects Hurrakify: from n/a through <= 2.4.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Server-Side Request Forgery (SSRF) vulnerability exists in Hurrakify up to version 2.4, allowing an attacker to make the server perform unintended requests to internal or external resources. The vulnerability has a CVSS score of 7.2 (HIGH), indicating significant potential impact on confidentiality and availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hurrakify versionLocate the Hurrakify installation and check its version identifier in the application metadata, configuration file, or admin interface. Common locations include version info in the footer, a /about page, config.xml, or package.json if it's a web app.Affected if The installed version is 2.4 or lower.
-
Locate URL request functionalitySearch the application for endpoints, APIs, or features that accept URL or URI input from users. Look for parameters named 'url', 'uri', 'link', 'redirect', 'src', or 'dest' in HTTP requests, or functions that perform HTTP client operations like file_get_contents, curl, or similar in the codebase.Affected if The application contains functionality that takes user-supplied URLs and makes server-side requests to them.
-
Test for SSRF in URL-handling featuresIf URL-handling features are found, inspect whether the application performs DNS lookups or makes HTTP requests to the supplied URL without strict validation. Check if internal network resources (127.0.0.1, 192.168.x.x, 10.x.x.x, localhost) or cloud metadata endpoints are reachable through this input.Affected if User-provided URLs can trigger server-side requests to arbitrary destinations, including internal infrastructure.
-
Review network configurationExamine whether the server running Hurrakify has outbound network access that would allow it to reach internal resources or make arbitrary HTTP requests as triggered by the SSRF vector.Affected if The server can make outbound HTTP requests and the vulnerable URL input feature is accessible to attackers.
You are affected if Hurrakify version 2.4 or lower is installed AND the application has URL-request functionality accessible to users that lacks strict allowlist-based validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and allowlist-based URL filtering to restrict server-side requests to trusted destinations only, and disable or restrict access to internal network resources.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54330 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data