dbcve.org
Ios XeOperating system · Cisco

CVE-2024-20316

MEDIUM · 5.3 CVSS v3.1 Published 2024-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 in the data model interface (DMI) services of Cisco IOS XE Software could allow an unauthenticated, remote attacker to access resources that should have been protected by a configured IPv4 access control list (ACL). This vulnerability is due to improper handling of error conditions when a successfully authorized device administrator updates an IPv4 ACL using the NETCONF or RESTCONF protocol, and the update would reorder access control entries (ACEs) in the updated ACL. An attacker could exploit this vulnerability by accessing resources that should have been protected across an affected device.

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

A vulnerability in Cisco IOS XE's data model interface (DMI) services allows unauthenticated remote attackers to bypass IPv4 ACL protection. The flaw stems from improper error handling when a privileged admin updates an IPv4 ACL via NETCONF or RESTCONF protocols in a way that reorders access control entries (ACEs), causing the ACL to fail open and expose protected resources.

MitigationApply Cisco IOS XE patches when available. Until then, restrict NETCONF/RESTCONF management access to trusted networks only, and carefully validate any ACL modifications to avoid triggering the ACE reordering condition.

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
Ios XeOperating system
Affected:= 16.3.1= 16.3.1a= 16.3.2= 16.3.3= 16.3.4= 16.3.5= 16.3.5b= 16.3.6= 16.3.7= 16.3.8= 16.3.9= 16.3.10

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Check the IOS XE version
    Execute 'show version' on the device and locate the version string (e.g., 16.3.x)
    Affected if The version matches one of the affected releases: 16.3.1 through 16.3.10 (including 16.3.1a, 16.3.5b)
  2. Verify NETCONF or RESTCONF is enabled
    Execute 'show netconf-yang configuration' and 'show restconf configuration' to check if DMI services are active
    Affected if NETCONF (port 830) or RESTCONF (port 443) services are enabled and reachable
  3. Identify IPv4 ACLs applied to management interfaces
    Execute 'show ip access-lists' and check which interfaces have IPv4 ACLs applied via 'show ip interface'
    Affected if IPv4 ACLs are configured on any interface, particularly management or management-facing interfaces
  4. Review recent ACL changes via NETCONF/RESTCONF
    Check device logs, audit logs, or configuration history for recent ACL modifications performed via DMI protocols
    Affected if Any ACL configuration changes were made via NETCONF or RESTCONF that may have triggered ACE reordering

The device is likely affected if it runs a vulnerable IOS XE 16.3.x version, has NETCONF/RESTCONF enabled, and has IPv4 ACLs that may have been modified via DMI protocols, as the ACE reordering condition causes the ACL to fail open.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco IOS XE patches when available. Until then, restrict NETCONF/RESTCONF management access to trusted networks only, and carefully validate any ACL modifications to avoid triggering the ACE reordering condition.

Fix this in Ios Xe Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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