/

CVE-2023-24215

Severity:

CRITICAL RISK

(9.1)

Improper Access Control in NOVUS AirGate 4G get Endpoint

CVE-2023-24215

Awaiting Analysis

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Administrative Account Compromise and Full Device Takeover

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

NOVUS AirGate 4G firmware v1.1.16 exposes administrator credentials through the /uci/get API endpoint due to incorrect access control.

An unauthenticated attacker can send a crafted POST request to this endpoint and retrieve sensitive configuration data, including admin login details, without prior authorization.

Affected context

This vulnerability appears in NOVUS AirGate 4G devices running firmware v1.1.16 where the /uci/get HTTP endpoint is reachable over the network.

It manifests when the endpoint is exposed without robust authentication and authorization checks, allowing configuration-related operations to be invoked by arbitrary clients.

The risk is elevated when the management interface is accessible from untrusted networks or the internet, or when segmentation and firewall rules are weak.

Exploit preconditions

  • Attack surface: Network-accessible management interface of the NOVUS AirGate 4G device (usually HTTP/HTTPS on the configured management port).
  • Required access: No prior authentication; the attacker only needs network-level reachability to the device.
  • Trigger point: Sending a crafted POST request to the /uci/get endpoint that requests configuration data containing administrator credentials.
  • Why exploitation is possible: The endpoint implements insufficient or missing authorization checks and exposes sensitive configuration responses to unauthenticated callers, violating least-privilege and proper access control boundaries.

Why this happens

The core issue aligns with CWE-284: Improper Access Control.

The /uci/get endpoint fails to enforce that only authenticated and properly authorized users can request and read sensitive configuration elements, such as administrator credentials.

In effect, the API treats any incoming POST request as trusted, exposing data that should be constrained to high-privilege sessions.

This design flaw reflects a broader pattern where configuration or diagnostic APIs are not given the same strict access control as interactive login flows, leading to inadvertent credential disclosure.

Potential impact

  • Unauthenticated retrieval of administrator usernames and passwords.
  • Full administrative control of the AirGate 4G device by an attacker.
  • Manipulation of network, modem, or routing settings, potentially disrupting connectivity.
  • Installation of malicious configurations that can enable persistent backdoors or traffic redirection.
  • Use of compromised devices as a pivot point into adjacent networks.

General mitigation guidance

Effective mitigation focuses on tightening access control and reducing exposure of sensitive management endpoints:

  • Enforce strong authentication and fine-grained authorization checks on all configuration/management endpoints, including non-interactive APIs like /uci/get.
  • Limit which configuration fields can be queried via APIs, avoiding direct exposure of credentials or secrets; prefer tokenized or indirect reference mechanisms.
  • Apply least-privilege design so that read operations are scoped and role-aware, and sensitive data is only accessible to explicitly privileged roles.
  • Place management interfaces behind dedicated management networks or VPNs, and restrict access via firewall rules and network segmentation.
  • Avoid storing or returning plaintext credentials where possible; instead, rely on secure hashing, key management systems, or device-bound secrets that are not directly retrievable.

How teams detect issues like this

Detection typically combines code-level review with network monitoring:

  • Static analysis and code review: Search for management or configuration endpoints that:
  • Bypass or weakly enforce authentication/authorization middleware.
  • Return configuration blobs or database records that contain credentials or secrets.
  • Use generic "get config" handlers without per-field access controls.
  • API design reviews: Examine REST/RPC interfaces for endpoints that can enumerate or dump configuration, and verify they consistently apply authentication and privilege checks.
  • Runtime monitoring: Use web application firewalls (WAF) or API gateways to log and alert on anomalous POST requests to configuration endpoints, especially from untrusted networks or unauthenticated sessions.
  • Security testing: Incorporate authorization testing in routine penetration tests and CI-driven security checks, specifically targeting management and configuration APIs.

Sources

SourceLink
github.comgithub.com/sql3t0/cve-disclosures/blob/main/00_-_CVE-2023-24215.md

Frequently asked

questions

Yes. If the management interface exposing /uci/get is reachable from an attacker-controlled network (e.g., the internet or an untrusted internal segment), the vulnerability can be exploited remotely without prior access.

The attacker only needs network access to the device's management interface; no valid credentials or existing session are required because the issue stems from missing or ineffective access control.

The most robust fix is to enforce mandatory authentication and authorization on all configuration endpoints, strictly limit which fields can be returned via APIs, and ensure that secrets or credentials are never exposed in plaintext responses.

Adopt a security-by-design approach: treat every management and configuration endpoint as sensitive, centralize authentication/authorization logic, apply least privilege for every API operation, and perform regular security reviews and tests focused on access control and data exposure.

Find out what's already
exploitable in your codebase.