dbcve.org
Solar Log 250 FirmwareOperating system · Solar Log

CVE-2022-47767

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to 4.2.8_117 / 5.1.2_156 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A backdoor in Solar-Log Gateway products allows remote access via web panel gaining super administration privileges to the attacker. This affects Solar-Log devices that use firmware version v4.2.7 up to v5.1.1 (included). This does not exist in 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

A detailed technical summary for this CVE is being prepared.

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
Solar Log 250 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 300 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 500 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 800e FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 1000 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 1000 Pm\+ FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 1200 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156
Solar Log 2000 FirmwareOperating system
Affected:< 4.2.8_117>= 5.0.0, < 5.1.2_156

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

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
Upgrade available Upgrade to 4.2.8_117 / 5.1.2_156 or later
Fixed in 4.2.8_1175.1.2_156
Recommended fix High confidence

Firmware version 4.2.8_117 or higher (4.x branch); or version 5.1.2_156 or higher (5.x branch)

  1. 1. Identify the specific Solar-Log device model (250, 300, 500, 800e, 1000, 1000 Pm+, 1200, or 2000)
  2. 2. Access the device's web management interface
  3. 3. Navigate to the firmware update or system settings section
  4. 4. Obtain the appropriate firmware version from the official Solar-Log website (www.solar-log.com)
  5. 5. Upload and install firmware version 4.2.8_117 or higher for the 4.x firmware branch
  6. 6. Alternatively, if currently on 5.x firmware, upgrade to version 5.1.2_156 or higher
  7. 7. Verify the firmware upgrade was successful by checking the version in the web interface
  8. 8. Confirm the backdoor functionality is no longer accessible
Caveat Review release notes for any configuration or feature changes between versions; firmware upgrades may require reconfiguration of existing settings

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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