Secuno
ENNL
Book demo

CVE-2024-32370

Hsclabs Mailinspector vulnerability

9.8 CRITICALPublic exploitEPSS 1.04%
  1. Published7 May 2024

Description

An issue in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a remote attacker to obtain sensitive information via a crafted payload to the id parameter in the mliSystemUsers.php component.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Hsclabs Mailinspector≥ 5.2.17-3 < 5.2.19

Remediation

Fixed in
Hsclabs Mailinspector≥ 5.2.19

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2024-3925110.0
An issue in the component ControlCenter.sys/ControlCenter64.sys of ThundeRobot Control…
CVE-2024-419610.0
An improper input validation vulnerability was discovered in Avaya IP Office that…
CVE-2024-332228.4
An issue in the component ATSZIO64.sys of ASUSTeK Computer Inc ASUS ATSZIO Driver…
CVE-2024-308049.8
An issue discovered in the DeviceIoControl component in ASUS Fan_Xpert before v.10013…
CVE-2021-215518.8
Dell dbutil_2_3.sys driver contains an insufficient access control vulnerability which…

Frequently asked

Is CVE-2024-32370 being actively exploited?

CVE-2024-32370 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.04%.

How severe is CVE-2024-32370?

CVE-2024-32370 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 1.04% probability of exploitation.

Which products are affected by CVE-2024-32370?

Affected products include Hsclabs Mailinspector.

How do I fix CVE-2024-32370?

Upgrade affected software to a fixed version, for example Hsclabs Mailinspector 5.2.19 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-32370 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.