Skip to main content
VulnerabilityPublished

CVE-2024-44076: microcks · Improper Privilege Management

Affects microcksSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.10.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade microcks/microcks to 1.10.0.

Affected software

ProductAffectedFixed in
GitHubmicrocks/microckspkg:github/microcks/microcksOther threatsAffected
  • <1.10.0
Fixed in
  • 1.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-44076, organizations should take immediate steps beyond generic advice: 1) Upgrade Microcks to version 1.10.0 or later once the patch is officially released to ensure proper access controls are enforced on the import/export endpoints. 2) Until a patch is available, restrict network access to Microcks API endpoints using firewall rules or VPNs to limit exposure only to trusted administrators. 3) Implement strong authentication and authorization mechanisms at the application or proxy level to prevent unauthorized users from accessing sensitive endpoints. 4) Monitor API logs for unusual import/export activity indicative of exploitation attempts. 5) Conduct internal audits of API definitions and mocks to detect unauthorized changes. 6) Integrate Microcks usage within secure development lifecycle practices, ensuring that only verified personnel have access to critical API management functions. 7) Consider deploying Web Application Firewalls (WAF) with custom rules to block suspicious POST requests to /api/import and /api/export endpoints. These targeted mitigations will reduce the risk of exploitation until a secure version is deployed.

Description

In Microcks before 1.10.0, the POST /api/import and POST /api/export endpoints allow non-administrator access.

References

Community reviews

Loading reviews…