Web Master FirmwareOperating system · Gesslergmbh

CVE-2024-1039

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Gessler GmbH WEB-MASTER has a restoration account that uses weak hard coded credentials and if exploited could allow an attacker control over the web management of the device.

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

Gessler GmbH WEB-MASTER devices contain a restoration account with weak hardcoded credentials embedded in the firmware. This account provides authenticated access to the device's web management interface, allowing remote attackers to gain full administrative control without discovering or cracking credentials.

MitigationImmediately restrict network access to the WEB-MASTER management interface, disable the restoration account if possible, contact Gessler GmbH for firmware updates that remove hardcoded credentials, and change any default passwords on all accounts.

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
Web Master FirmwareOperating system
Affected:= 7.9

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 firmware version
    Access the device's web management interface or check the system information page to determine the installed firmware version. Consult the device documentation for the specific location of version information.
    Affected if The installed firmware version is 7.9 (Gesslergmbh Web Master Firmware)
  2. Review user accounts in the web interface
    Log into the web management interface and navigate to the user account or administration section. Look for any accounts labeled as 'restoration', 'recovery', 'service', or similar that are not explicitly created by your organization.
    Affected if A restoration account or any undocumented administrative account exists in the user list
  3. Verify network exposure of management interface
    Determine if the WEB-MASTER web management interface is accessible from untrusted networks (such as the public internet) by reviewing firewall rules, port forwards, or performing an external port scan for HTTP/HTTPS services.
    Affected if The management interface is exposed to untrusted networks without VPN or IP restriction controls
  4. Check for default or unchanged credentials
    Attempt to log in using any documentation-provided default credentials, or check if password policies are being enforced on all accounts in the system.
    Affected if Default passwords remain unchanged or weak credentials are in use
  5. Inspect firmware for embedded credentials
    If you have access to the firmware image (through backup, update file, or device extraction), examine the firmware binary or configuration files for hardcoded username and password strings.
    Affected if Hardcoded credentials or restoration account details are found embedded in the firmware

A user is affected if the device runs Gesslergmbh Web Master Firmware version 7.9 and has the undocumented restoration account accessible on the web management interface.

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

Immediately restrict network access to the WEB-MASTER management interface, disable the restoration account if possible, contact Gessler GmbH for firmware updates that remove hardcoded credentials, and change any default passwords on all accounts.

Fix this in Web Master Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1039 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1039 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