dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-40117

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-26
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
Incorrect access control in Solar-Log 1000 before v2.8.2 and build 52- 23.04.2013 allows attackers to obtain Administrative privileges via connecting to the web administration server. Not existing for SL 200, 500, 1000 / fixed in 4.2.8 for SL 250, 300, 1200, 2000, SL 50 Gateway / fixed in 5.1.2 / 6.0.0 for SL Base.

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 confidence

Incorrect access control vulnerability in Solar-Log 1000 web administration interface allows unauthenticated attackers to gain Administrative privileges by directly connecting to the device's web server. This is a privilege escalation issue where the access control mechanism fails to properly restrict administrative functions.

MitigationUpdate Solar-Log 1000 to firmware v2.8.2 or later (build 52-23.04.2013 or newer). For other affected models (SL 250, 300, 1200, 2000, SL 50 Gateway), apply the appropriate patched versions (4.2.8, 5.1.2, or 6.0.0 depending on model). If updates cannot be applied immediately, restrict network access to the web administration port.

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
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 Solar-Log device model
    Access the web administration interface or check device documentation to confirm the exact model (Solar-Log 1000, SL 250, 300, 1200, 2000, or SL 50 Gateway)
    Affected if The device is NOT one of these models - the CVE does not apply
  2. Determine the installed firmware version
    Log into the web interface and navigate to the 'System' or 'Status' page to view the firmware version and build date
    Affected if The firmware version is at or above the patched version for your model (v2.8.2 for Solar-Log 1000, or 4.2.8/5.1.2/6.0.0 for other models) - you are NOT affected
  3. Verify web administration port exposure
    Attempt to access the device's web interface from an external network location or use a network scan to confirm port 80/443 is accessible from untrusted networks
    Affected if The web administration port is ONLY accessible from trusted internal networks - exploitation is significantly harder but the vulnerability may still exist if an attacker can reach the web server
  4. Test for unauthenticated admin access
    Send an HTTP request directly to the device's web server endpoint (such as /admin or a configuration API endpoint) without providing any authentication credentials
    Affected if The request succeeds and returns administrative functionality or configuration options without any login prompt - you ARE affected

You are affected if you run a Solar-Log 1000, SL 250, 300, 1200, 2000, or SL 50 Gateway with firmware below the patched versions AND the web administration interface is network-accessible to untrusted parties.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Solar-Log 1000 to firmware v2.8.2 or later (build 52-23.04.2013 or newer). For other affected models (SL 250, 300, 1200, 2000, SL 50 Gateway), apply the appropriate patched versions (4.2.8, 5.1.2, or 6.0.0 depending on model). If updates cannot be applied immediately, restrict network access to the web administration port.

Recommended fix Moderate confidence

Firmware v2.8.2 (SL 1000), v4.2.8 (SL 250/300/1200/2000/SL 50 Gateway), or v5.1.2/v6.0.0 (SL Base)

  1. 1. Identify the specific Solar-Log device model (SL 1000, SL 250, SL 300, SL 1200, SL 2000, SL 50 Gateway, or SL Base)
  2. 2. Access the device's web administration interface
  3. 3. Navigate to the firmware version or system information section
  4. 4. Download the appropriate firmware update: For SL 1000 use v2.8.2 (build 52-23.04.2013), For SL 250/300/1200/2000/SL 50 Gateway use v4.2.8, For SL Base use v5.1.2 or v6.0.0
  5. 5. Upload and apply the firmware update via the web interface or device management console
  6. 6. After update, verify the firmware version has been successfully applied
  7. 7. Confirm administrative access controls are functioning correctly
Caveat Firmware updates may reset device configuration to defaults; backup configuration before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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