A flaw has been found in D-Link DIR-825M 1.1.8. This impacts the function sub_41802C of the file /boafrm/formLtefotaUpgradeFibocom of the component LTE Module Firmware Upgrade. This manipulation of the argument fota_url causes stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been published and may be used.
Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in the D-Link DIR-825M firmware upgrade interface can corrupt device memory when a low-privileged user supplies a malicious firmware URL. Successful exploitation could compromise confidentiality, integrity, and availability. The evidence identifies firmware 1.1.8 only.
Executive priority
Treat confirmed DIR-825M 1.1.8 deployments as an urgent remediation priority, especially when management interfaces are externally reachable or accessible from untrusted networks. Prioritize exposure reduction immediately while confirming vendor guidance. Do not describe the issue as actively exploited without further evidence.
Technical view
The fota_url argument processed by sub_41802C in /boafrm/formLtefotaUpgradeFibocom can trigger a stack-based buffer overflow. CVSS 3.1 rates it 9.9, reflecting network access, low complexity, low privileges, no user interaction, changed scope, and high impact.
Likely exposure
Exposure is most likely where a DIR-825M running firmware 1.1.8 permits a low-privileged account to reach the LTE Module Firmware Upgrade handler. Internet exposure or access from untrusted networks increases risk. Other models and versions are not established by the supplied evidence.
Exploitation context
A public exploit report exists, so reproduction knowledge may be available. The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Authentication with low privileges is indicated by the CVSS vector.
Researcher notes
The record maps the issue to CWE-119 and CWE-121. Evidence names one handler, argument, model, and firmware version. Public exploit availability increases practical concern, but successful code execution, observed attacks, patch status, and applicability to other versions are not established by the supplied material.
Mitigation direction
Inventory DIR-825M devices and identify those running firmware 1.1.8.
Restrict management access to trusted administrators and isolated management networks.
Remove the administration interface from direct internet exposure.
Check D-Link guidance for corrected firmware or vendor-approved mitigation.
If no safe remediation exists, consider replacing or isolating affected devices.
Validation and detection
Confirm the exact device model and installed firmware through trusted administrative records.
Review network controls governing access to the device administration interface.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.