/

CVE-2025-45422

Severity:

HIGH RISK

(8.1)

Access Control Flaw (CWE-284) in Proximus b-box Router

CVE-2025-45422

Deferred

Vulnerability type

Category:

Access Control Misconfiguration

CWE:

CWE-284

Impact:

Unauthorized Configuration Manipulation and Network Exposure

Severity:

HIGH RISK

(8.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

Incorrect access control in the Proximus b-box router allows authenticated users to bypass normal restrictions on managing port forwarding rules.

Under certain interface or role conditions, an attacker with valid access can make arbitrary changes to NAT/port forwarding configuration, expanding network exposure beyond intended limits.

Affected context

This vulnerability occurs in the management interface of Proximus b-box devices where role-based or functional restrictions are intended to limit how users can change port forwarding rules.

It is relevant when the router is administered through a web UI or remote management channel that relies on access control checks to enforce which configuration options a user can modify.

Deployments that expose the administration interface to multiple users or external networks, and that rely on the device to maintain strict NAT boundaries, are more likely to be affected.

Exploit preconditions

  • Attack surface: Router management interface (typically web-based UI or equivalent control channel)
  • Required access: Authenticated access to the b-box administration interface (e.g., valid credentials or session)
  • Trigger point: Interaction with port forwarding/NAT configuration pages or APIs that fail to enforce intended restrictions
  • Why exploitation is possible: Access control checks on who can modify port forwarding rules are incomplete or incorrectly implemented, allowing an authenticated user to perform actions beyond their authorized scope

Why this happens

The underlying bug belongs to the access control category (CWE-284), where the system fails to properly enforce restrictions on sensitive configuration operations.

In this case, logic responsible for validating whether a given authenticated user is allowed to create, modify, or delete port forwarding rules does not correctly constrain those actions.

As a result, the router trusts requests that should be denied or limited, effectively treating any authenticated session as sufficiently privileged to change network exposure settings.

Potential impact

  • An authenticated user may reconfigure port forwarding to expose internal devices to the internet.
  • Attackers could create rules that enable unsolicited inbound connections to services that were intended to remain private.
  • Misuse of port forwarding settings can facilitate further attacks such as unauthorized remote access or service enumeration on internal hosts.
  • The router's role as a boundary device can be undermined, potentially weakening overall network security posture.

General mitigation guidance

Effective mitigations focus on strengthening access control logic and reducing trust in authenticated sessions by default.

Common defensive patterns include:

  • Implementing strict role-based authorization checks around high-impact configuration operations such as port forwarding and firewall rules.
  • Centralizing access control decisions to avoid inconsistent checks between the UI and underlying APIs.
  • Designing the management interface so that sensitive configuration features are disabled or hidden unless explicitly granted by a higher-privileged role.
  • Applying least-privilege principles to all user accounts, ensuring that routine users cannot alter boundary-defining settings.
  • Restricting exposure of the administration interface (e.g., limiting it to trusted management networks) to reduce the pool of potential authenticated attackers.

How teams detect issues like this

Detection typically involves reviewing how authorization is enforced around configuration endpoints and verifying that privilege boundaries are respected.

Useful approaches include:

  • Static analysis or manual code review aimed at identifying configuration-modifying functions that lack robust authorization checks.
  • Policy-based tests that exercise the management UI and APIs with users of different roles to confirm that unauthorized changes to port forwarding rules are rejected.
  • Logging and monitoring of administrative actions, with alerts on unexpected or high-risk changes to NAT and firewall settings.
  • Automated security testing of router firmware interfaces to detect inconsistent access control enforcement across different configuration paths.

Sources

SourceLink
b-box.comb-box.com
proximus.comproximus.com
github.comgithub.com/Cedrico03/CVE-2025-45422---Bbox
nvd.nist.govnvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:H/RL:U/RC:C/CR:H/IR:H/AR:H/MAV:N/MAC:L/MPR:N/MUI:N/MS:C/MC:H/MI:H/MA:H&version=3.1

Frequently asked

questions

It can be, if the router's management interface is exposed to the internet or reachable from untrusted networks. However, exploitation still requires authenticated access, not purely unauthenticated remote access.

The attacker needs valid authenticated access to the b-box management interface. This could be a standard user account, shared credentials, or a compromised administrative session, depending on how the device is deployed.

The safest pattern is to enforce strict, centralized authorization checks around all configuration changes, ensuring that only explicitly authorized roles can modify port forwarding and similar boundary-defining settings, and that all paths to such operations share the same access control logic.

Prevention strategies include designing with least privilege, performing systematic authorization reviews on all configuration APIs, implementing consistent role-based access control, and routinely testing administrative interfaces with security-focused test cases and automated tools.

Find out what's already
exploitable in your codebase.