dbcve.org
IsherlockApplication · Hgiga

CVE-2023-37292

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-21
Fix available
A fix is available. Upgrade to 4.5-174 / 5.5-174 or later.
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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in HGiga iSherlock 4.5 (iSherlock-user modules), HGiga iSherlock 5.5 (iSherlock-user modules) allows OS Command Injection.This issue affects iSherlock 4.5: before iSherlock-user-4.5-174; iSherlock 5.5: before iSherlock-user-5.5-174.

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

HGiga iSherlock versions 4.5 and 5.5 contain an OS Command Injection vulnerability in the iSherlock-user modules. User-supplied input is not properly sanitized before being passed to operating system commands, allowing remote attackers to execute arbitrary OS commands on the affected system. The vulnerability affects iSherlock 4.5 before version iSherlock-user-4.5-174 and iSherlock 5.5 before version iSherlock-user-5.5-174.

MitigationApply the vendor-supplied patches: upgrade to iSherlock-user-4.5-174 or later for version 4.5, or iSherlock-user-5.5-174 or later for version 5.5. If immediate patching is not possible, implement network segmentation and restrict access to the iSherlock management interfaces to reduce exposure.

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
IsherlockApplication
Affected:>= 4.5, < 4.5-174>= 5.5, < 5.5-174

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 HGiga iSherlock installation
    Locate the iSherlock installation directory or check system inventory for HGiga iSherlock software. Common locations may include /opt/isherlock or program files in Windows. Check for iSherlock-related services running on the system.
    Affected if iSherlock software is present on the system
  2. Determine installed iSherlock version
    Access the iSherlock management interface or check version information via the application's about page, version command, or configuration files. Look for the exact version number such as 4.5.x or 5.5.x.
    Affected if The installed version is 4.5 or 5.5 (any subversion)
  3. Confirm iSherlock-user module is present
    Verify that the iSherlock-user module is installed and available. This is the specific module where the command injection vulnerability exists. Check module listings in the iSherlock admin console or configuration.
    Affected if The iSherlock-user module is installed and enabled
  4. Compare version against affected ranges
    Compare your installed version number to the vulnerable ranges: version 4.5 before build 174 (iSherlock-user-4.5-174) and version 5.5 before build 174 (iSherlock-user-5.5-174). If your build number is 174 or higher, you have the patched version.
    Affected if Installed version is iSherlock 4.5 < iSherlock-user-4.5-174 OR iSherlock 5.5 < iSherlock-user-5.5-174

The environment is affected if HGiga iSherlock version 4.5 or 5.5 is installed with the iSherlock-user module and the build version is below 174.

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
Upgrade available Upgrade to 4.5-174 / 5.5-174 or later
Fixed in 4.5-1745.5-174
Interim mitigation

Apply the vendor-supplied patches: upgrade to iSherlock-user-4.5-174 or later for version 4.5, or iSherlock-user-5.5-174 or later for version 5.5. If immediate patching is not possible, implement network segmentation and restrict access to the iSherlock management interfaces to reduce exposure.

Recommended fix High confidence

iSherlock-user-4.5-174 (for 4.x) or iSherlock-user-5.5-174 (for 5.x)

  1. Identify currently installed iSherlock version using system inventory or version check command
  2. For iSherlock 4.x: Upgrade to iSherlock-user-4.5-174 or later
  3. For iSherlock 5.x: Upgrade to iSherlock-user-5.5-174 or later
  4. Apply the upgrade following HGiga's standard upgrade procedure
  5. Verify the installation completed successfully
  6. Confirm the new version is running post-upgrade

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

Fix this in Isherlock Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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