dbcve.org
Poly Clariti ManagerApplication · Hp

CVE-2024-41912

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-07
Fix available
A fix is available. Upgrade to 10.12.0.2_100 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
A vulnerability was discovered in the firmware builds up to 10.10.2.2 in Poly Clariti Manager devices. The firmware flaw does not properly implement access controls.

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 · moderate confidence

A critical access control vulnerability exists in Poly Clariti Manager firmware versions up to 10.10.2.2. The flaw allows unauthorized access to sensitive management functions due to improper implementation of access controls, likely enabling unauthenticated attackers to gain administrative privileges or access to confidential data.

MitigationUpdate Poly Clariti Manager firmware to a version beyond 10.10.2.2 once the vendor releases a patch. If no patch is available, restrict network access to the management interface using firewall rules or VPN access controls.

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
Poly Clariti ManagerApplication
Affected:< 10.12.0.2_100

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 if Poly Clariti Manager is running
    Access the system administration interface or check running services on the device hosting Poly Clariti Manager. Look for the Clariti Manager service or web interface.
    Affected if The Poly Clariti Manager service or web interface is active on the system.
  2. Determine the installed firmware version
    Log into the Poly Clariti Manager web interface and navigate to the Settings or About section, typically found under System Administration or Help > About. Alternatively, check the firmware version displayed on the login page or in the system dashboard.
    Affected if The displayed firmware version is visible.
  3. Compare version against affected range
    Compare the installed version number to the affected range: any version lower than 10.12.0.2_100 is affected. Versions 10.10.2.2 and below are explicitly mentioned as vulnerable in the summary.
    Affected if The installed version is 10.12.0.2_100 or lower, or any version up to and including 10.10.2.2.
  4. Assess management interface exposure
    Determine if the Poly Clariti Manager web interface is accessible from untrusted networks. Check firewall rules, NAT configurations, or VPN policies that control access to port 443 or the management web port.
    Affected if The management interface is accessible from public or untrusted network segments without VPN or IP restriction.
  5. Review for unauthorized admin accounts
    If access is available, review the user accounts list in the management interface under Administration or User Management. Look for unexpected accounts, especially those with Administrator privileges that were not created by your organization.
    Affected if Unexpected administrator-level accounts exist in the system.

A system is affected if Poly Clariti Manager firmware version is 10.12.0.2_100 or lower AND the management interface is accessible to untrusted networks, allowing potential unauthorized administrative access.

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 10.12.0.2_100 or later
Fixed in 10.12.0.2_100
Interim mitigation

Update Poly Clariti Manager firmware to a version beyond 10.10.2.2 once the vendor releases a patch. If no patch is available, restrict network access to the management interface using firewall rules or VPN access controls.

Recommended fix Moderate confidence

10.12.0.2_100

  1. Obtain the Poly Clariti Manager firmware version 10.12.0.2_100 from the official HP support portal at support.hp.com
  2. Review the firmware upgrade documentation specific to Poly Clariti Manager
  3. Schedule a maintenance window as firmware updates may require downtime
  4. Back up the current configuration following vendor backup procedures
  5. Upload and apply firmware version 10.12.0.2_100 to the Poly Clariti Manager device
  6. Verify the firmware version has been successfully applied post-upgrade
  7. Confirm the access control vulnerability is resolved by testing authenticated access controls

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

Fix this in Poly Clariti Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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