CVE-2024-24215
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 · uneditedAn issue in the component /cgi-bin/GetJsonValue.cgi of Cellinx NVT Web Server 5.0.0.014 allows attackers to leak configuration information via a crafted POST request.
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 confidenceThe Cellinx NVT Web Server 5.0.0.014 contains an information disclosure vulnerability in the /cgi-bin/GetJsonValue.cgi component. Attackers can craft malicious POST requests to this CGI endpoint to leak sensitive configuration information from the server. The medium severity (5.3) indicates the disclosure is limited in scope but still provides actionable intelligence for further attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.0.0.014CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Cellinx NVT Web Server versionCheck the server's version information through its admin interface, HTTP banner, or by inspecting installed software metadata. The exact version can often be obtained from the server's about page, headers, or installed program files.Affected if The installed version is exactly 5.0.0.014
-
Verify CGI module is enabledCheck the web server configuration files or admin interface to confirm the CGI module is active. Look for entries enabling CGI execution in httpd.conf, nginx.conf (with fcgiwrap), or the equivalent configuration file.Affected if CGI execution is permitted on the server
-
Confirm GetJsonValue.cgi endpoint existsInspect the /cgi-bin/ directory on the web server and verify that GetJsonValue.cgi file is present. This can be done via directory listing checks, file system inspection, or attempting to access the endpoint.Affected if The file /cgi-bin/GetJsonValue.cgi exists on the server
-
Test endpoint accessibility via POST requestSend a crafted POST request to http://[target]/cgi-bin/GetJsonValue.cgi and observe the response. A vulnerable server will return sensitive configuration data in JSON format.Affected if The endpoint responds to POST requests with configuration or sensitive data
-
Check network exposure of CGI-bin directoryVerify whether the /cgi-bin/ directory is accessible from untrusted networks. Review firewall rules, ACLs, or network segmentation that may limit access to this endpoint.Affected if The CGI endpoint is reachable from external or untrusted networks
You are affected if you are running Cellinx NVT Web Server version 5.0.0.014, the CGI module is enabled, and the /cgi-bin/GetJsonValue.cgi endpoint is accessible on your network.
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 dataApply vendor patches when available; until then, restrict network access to the /cgi-bin/ endpoint, implement strict input validation on GetJsonValue.cgi, and consider disabling the CGI component if not required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24215 — 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-24215 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