dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2023-24215

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Incorrect access control in the /uci/get/ endpoint of NOVUS AirGate 4G firmware v1.1.16 allows unauthenticated attackers to obtain administrator credentials via a crafted POST request.

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

NOVUS AirGate 4G firmware v1.1.16 contains an incorrect access control vulnerability in the /uci/get/ endpoint. The endpoint fails to enforce authentication, allowing unauthenticated attackers to submit crafted POST requests and retrieve administrator credentials in plaintext.

MitigationApply vendor firmware patch when available; prior to patch deployment, restrict network access to the /uci/get/ endpoint via firewall or access control lists to prevent unauthenticated access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm device is NOVUS AirGate 4G
    Identify the device through web interface, SNMP, network scanning, or device labeling
    Affected if Device is not NOVUS AirGate 4G - not affected
  2. Check firmware version
    Access device web interface or CLI and retrieve firmware version; compare to v1.1.16
    Affected if Version is v1.1.16 - likely affected; other versions - not affected unless backported
  3. Test /uci/get/ endpoint accessibility
    Send a POST request to http://<device-ip>/uci/get/ without any authentication headers or credentials
    Affected if Endpoint returns a response without requiring authentication - potentially affected
  4. Check for credential exposure
    If endpoint responds, examine the response body for administrator usernames and passwords in plaintext
    Affected if Response contains plaintext admin credentials - confirmed affected

User is affected if device is NOVUS AirGate 4G running firmware v1.1.16 and the /uci/get/ endpoint accepts unauthenticated requests that expose admin credentials in plaintext

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 vendor firmware patch when available; prior to patch deployment, restrict network access to the /uci/get/ endpoint via firewall or access control lists to prevent unauthenticated access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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