Security Resilience

CVE-2023-49593

Level1 Wbr-6013 Firmware rer4_a_v3411b_2t2r_lev_09_170623

Published
08 July 2024
Modified
04 November 2025
CVSS Score v3.1 7.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.011 64th percentile
Risk Priority 55 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-49593 is a high-severity Active Debug Code (CWE-489) vulnerability in Level1 Wbr-6013 Firmware. Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

Leftover debug code exists in the boa formSysCmd functionality of LevelOne WBR-6013 RER4_A_v3411b_2T2R_LEV_09_170623. A specially crafted network request can lead to arbitrary command execution.

CWE(s)
CWE-489NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
attack.mitre.org →
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
attack.mitre.org →
T1020.001 Traffic Duplication Exfiltration
Adversaries may leverage traffic mirroring in order to automate data exfiltration over compromised infrastructure.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-46685Same product: Level1 Wbr-6013
CVE-2023-47856Same product: Level1 Wbr-6013
CVE-2023-49595Same product: Level1 Wbr-6013
CVE-2023-48270Same product: Level1 Wbr-6013
CVE-2023-41251Same product: Level1 Wbr-6013
CVE-2023-50243Same product: Level1 Wbr-6013
CVE-2023-50239Same product: Level1 Wbr-6013
CVE-2023-50244Same product: Level1 Wbr-6013
CVE-2023-50330Same product: Level1 Wbr-6013
CVE-2023-45215Same product: Level1 Wbr-6013

Affected Assets

level1
wbr-6013 firmware
rer4_a_v3411b_2t2r_lev_09_170623

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CM-2 Baseline Configuration partial match

Baseline configuration defines the approved production state that must exclude active debug code.

CM-7 Least Functionality partial match

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can require removal of debug code before release.

SA-3 System Development Life Cycle partial match

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices including secure coding, security testing, checkpoints, and developer training that reduce the chance of shipping active debug code, but does not guarantee its absence in every release (e.g. via incomplete enforcement or outsourced gaps).

A.8.26 Application security requirements partial match
removes
A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance catches active debug code before deployment.

A.8.31 Separation of development, test and production environments partial match
blocks

A.8.31 separates environments and controls movement between them but does not stop active debug code from remaining present and exploitable in a released production build

References