dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-36444

HIGH · 8.1 CVSS v3.1 Published 2024-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
No privileges Zero-click

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 · unedited
cgi-bin/fdmcgiwebv2.cgi on Swissphone DiCal-RED 4009 devices allows an unauthenticated attacker to gain access to device logs.

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 · high confidence

The fdmcgiwebv2.cgi script on Swissphone DiCal-RED 4009 devices lacks authentication controls, allowing any unauthenticated remote attacker to access sensitive device logs through this CGI endpoint.

MitigationImplement proper authentication and authorization controls on the fdmcgiwebv2.cgi endpoint, or network-segment the device management interface to prevent unauthorized external access.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device label, web interface, or system information to confirm the device is a Swissphone DiCal-RED 4009
    Affected if The device is a Swissphone DiCal-RED 4009 model
  2. Verify the CGI endpoint exists
    Attempt to access the URI /fdmcgiwebv2.cgi (or common variants like /cgi-bin/fdmcgiwebv2.cgi) on the device web server
    Affected if The endpoint returns an HTTP response (200, 401, or other) indicating it exists on the device
  3. Test for authentication bypass
    Send an HTTP request to the fdmcgiwebv2.cgi endpoint without providing any authentication credentials (no Authorization header, no session cookie, no login parameters)
    Affected if The endpoint returns HTTP 200 with content (such as log data) without requiring any login or credentials
  4. Inspect returned content for sensitive data
    Examine the response body from the unauthenticated request to determine if device logs, system messages, or other sensitive information are exposed
    Affected if Log files, system diagnostics, or sensitive device data are visible in the response without authentication

A user is affected if they have a Swissphone DiCal-RED 4009 device where the fdmcgiwebv2.cgi endpoint is accessible and returns sensitive log data without requiring any authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization controls on the fdmcgiwebv2.cgi endpoint, or network-segment the device management interface to prevent unauthorized external access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36444 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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