Cyber Resilience

CVE-2025-29062

RCE in Lb-Link Bl-Ac2100 Firmware ≤ 1.0.4

Public PoCRCECommand Injection
Published
02 April 2025
Modified
29 April 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.010 60th percentile
Risk Priority 82 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-2025-29062 is a critical-severity Command Injection (CWE-77) vulnerability in Lb-Link Bl-Ac2100 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-29062 is a command-injection vulnerability (CWE-77) affecting the BL-AC2100 router firmware at version V1.0.4 and earlier. Unauthenticated remote attackers can supply crafted values to the time1 and time2 parameters of the set_LimitClient_cfg function exposed by the embedded goahead web service, resulting in arbitrary code execution on the device.

Because the flaw is reachable over the network without credentials or user interaction, an attacker who can reach the web interface can obtain full control of the router, including the ability to read or modify any data and to use the device as a foothold for further attacks. The vulnerability carries a CVSS 3.1 base score of 9.8.

Public references consist of technical write-ups hosted on yuque.com that describe the injection vector; no vendor advisory or firmware patch addressing the issue is referenced in the available sources. The EPSS score rose from lower values after disclosure to a peak of 0.1435 on 2026-05-13 before receding to the current 0.0771, indicating a measurable increase in exploitation interest following publication.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

An issue in BL-AC2100 <=V1.0.4 allows a remote attacker to execute arbitrary code via the time1 and time2 parameters in the set_LimitClient_cfg of the goahead webservice.

CWE(s)
CWE-77

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-29063Same product: Lb-Link Bl-Ac2100
CVE-2025-10773Same product: Lb-Link Bl-Ac2100
CVE-2023-26801Same vendor: Lb-Link
CVE-2025-1610Same vendor: Lb-Link
CVE-2025-1608Same vendor: Lb-Link
CVE-2025-1609Same vendor: Lb-Link
CVE-2025-9580Same vendor: Lb-Link
CVE-2026-4228Same vendor: Lb-Link
CVE-2026-32241Shared CWE-77
CVE-2024-29864Shared CWE-77

Affected Assets

lb-link
bl-ac2100 firmware
≤ 1.0.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly stops construction of commands from untrusted data containing special elements.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include proper neutralization and safe command construction practices.

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 mostly match
prevents

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

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.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

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

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

References