dbcve.org
Axis Os 2024Operating system · Axis

CVE-2024-6979

HIGH · 7.5 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 11.11.94 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Amin Aliakbari, member of the AXIS OS Bug Bounty Program, has found a broken access control which would lead to less-privileged operator- and/or viewer accounts having more privileges than designed. The risk of exploitation is very low as it requires complex steps to execute, including knowing of account passwords and social engineering attacks in tricking the administrator to perform specific configurations on operator- and/or viewer-privileged accounts. Axis has released patched AXIS OS a version for the highlighted flaw. Please refer to the Axis security advisory for more information and solution.

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

Broken access control vulnerability in AXIS OS allows lower-privileged operator and viewer accounts to obtain elevated privileges beyond their intended permissions through specific configuration manipulations tricking administrators.

MitigationApply the patched AXIS OS version from Axis security advisory and audit existing operator/viewer account configurations for unauthorized privilege escalation.

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
Axis Os 2024Operating system
Affected:>= 11.11.0, < 11.11.94

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 AXIS OS version
    Access the device web interface or use the AXIS Device Manager to view the system information. The firmware version is displayed on the overview or system page.
    Affected if The installed version is 11.11.0 or higher but lower than 11.11.94
  2. Review user account configurations
    Navigate to Settings > Users or the equivalent user management section in the AXIS device web interface. List all configured accounts and their assigned roles.
    Affected if Operator or viewer accounts exist alongside administrator accounts in the system
  3. Audit account permissions and groups
    Examine each non-administrator account's assigned privileges, focusing on operator and viewer roles. Check whether any accounts have permissions that appear elevated beyond the standard operator or viewer baseline.
    Affected if Any operator or viewer account shows permissions inconsistent with the standard role definition, indicating potential unauthorized privilege escalation
  4. Inspect system configuration for manipulation indicators
    Review the device configuration files or audit logs for changes related to user permissions, group memberships, or access control settings. Look for recent modifications that may have been made through configuration manipulation.
    Affected if Recent or unexpected configuration changes involving user privilege settings are present in the audit log

You are affected if your AXIS OS version is 11.11.0 through 11.11.93 and you have operator or viewer accounts whose permissions appear elevated beyond their intended role.

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

Apply the patched AXIS OS version from Axis security advisory and audit existing operator/viewer account configurations for unauthorized privilege escalation.

Recommended fix Moderate confidence

AXIS OS 11.11.94 or later (2024 LTS track)

  1. Identify the current AXIS OS version running on the device using the device web interface or AXIS Device Manager
  2. Access the device administration panel and navigate to Settings > System > Maintenance
  3. Under the firmware upgrade section, upload and install AXIS OS version 11.11.94 or later
  4. After upgrade, verify the new version is installed and confirm that operator/viewer accounts no longer have elevated privileges
  5. Document the upgrade in change management system

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

Fix this in Axis Os 2024 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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