dbcve.org
IsherlockApplication · Hgiga

CVE-2024-4298

HIGH · 7.2 CVSS v3.1 Published 2024-04-29
Fix available
A fix is available. Upgrade to 4.5-188 / 5.5-188 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
The email search interface of HGiga iSherlock (including MailSherlock, SpamSherock, AuditSherlock) fails to filter special characters in certain function parameters, allowing remote attackers with administrative privileges to exploit this vulnerability for Command Injection attacks, enabling execution of arbitrary system commands.

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 (including MailSherlock, SpamSherock, AuditSherlock) contains a command injection vulnerability in its email search interface. The application fails to properly filter or sanitize special characters in certain function parameters used in the search functionality. Attackers with administrative privileges can inject arbitrary OS commands through these unsanitized inputs, achieving remote code execution on the affected system.

MitigationImplement strict input validation and sanitization for all function parameters in the email search interface, filtering or escaping shell metacharacters. If available, apply vendor-supplied security patches. Consider implementing allowlist validation for permitted characters and disabling system command execution capabilities in the search functionality.

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-188>= 5.5, < 5.5-188

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm HGiga iSherlock installation
    Identify whether any HGiga iSherlock product (Isherlock, MailSherlock, SpamSherock, or AuditSherlock) is deployed in the environment. Check installed software inventory or product documentation.
    Affected if The product is present in the environment.
  2. Determine installed version
    Locate and retrieve the installed version number of the HGiga iSherlock product. Compare against the affected ranges: version 4.5 through 4.5-188, or version 5.5 through 5.5-188.
    Affected if The installed version falls within >= 4.5 and < 4.5-188, or >= 5.5 and < 5.5-188.
  3. Verify email search interface is accessible
    Confirm that the email search functionality is enabled and accessible to administrative users. This may involve checking application configuration, module status, or web interface availability.
    Affected if The email search interface is enabled and accessible.
  4. Confirm administrative access exists
    Determine whether any account with administrative privileges exists or can access the system. The command injection requires administrative privileges to exploit.
    Affected if Administrative-level access to the email search feature is available.

A user is affected if they run a vulnerable iSherlock version within the specified ranges and have administrative access to the email search interface where the command injection can be triggered.

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-188 / 5.5-188 or later
Fixed in 4.5-1885.5-188
Interim mitigation

Implement strict input validation and sanitization for all function parameters in the email search interface, filtering or escaping shell metacharacters. If available, apply vendor-supplied security patches. Consider implementing allowlist validation for permitted characters and disabling system command execution capabilities in the search functionality.

Recommended fix Moderate confidence

4.5-188 or 5.5-188 (or respective later versions)

  1. Upgrade Isherlock version 4.5.x to version 4.5-188 or later
  2. Upgrade Isherlock version 5.5.x to version 5.5-188 or later
  3. After upgrade, verify the email search interface functions correctly
  4. Confirm the special character filtering is working in the email search parameters

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

Fix this in Isherlock 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 the upgrade done

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-4298 — 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-4298 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