CVE-2024-33832
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 · uneditedOneNav v0.9.35-20240318 was discovered to contain a Server-Side Request Forgery (SSRF) via the component /index.php?c=api&method=get_link_info.
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 confidenceOneNav version 0.9.35-20240318 contains a Server-Side Request Forgery (SSRF) vulnerability in the API endpoint /index.php?c=api&method=get_link_info. This allows an attacker to induce the server to make arbitrary requests to internal or external resources by manipulating input parameters, potentially accessing internal services, bypassing firewalls, or exfiltrating data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 OneNav installationLocate OneNav web application files in your web server's document root or application directory. Look for the presence of index.php and the OneNav directory structure.Affected if OneNav is present on the server
-
Check installed OneNav versionInspect the version information file, header, or configuration file within the OneNav installation. Compare the discovered version against 0.9.35-20240318.Affected if The installed version matches or exceeds 0.9.35-20240318 but is earlier than any patched release
-
Verify API endpoint accessibilityConfirm that the endpoint /index.php?c=api&method=get_link_info is accessible from the network or localhost. Check web server access logs for requests to this endpoint.Affected if The API endpoint is reachable and responds to requests
-
Test get_link_info method availabilitySend a GET or POST request to the get_link_info API method with a test parameter (such as a URL parameter) and observe if the server attempts to make an outbound request.Affected if The method accepts URL parameters and the server makes outbound HTTP requests based on those parameters
A user is affected if OneNav version 0.9.35-20240318 is installed and the get_link_info API endpoint is accessible and processes URL parameters by making outbound requests.
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 employ an allowlist approach for URLs permitted in the get_link_info API method. Additionally, restrict server-side request capabilities to trusted domains and disable unnecessary outbound connections from the application server.
- 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-33832 — 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-33832 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