CVE-2025-4733
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability, which was classified as critical, has been found in TOTOLINK A3002R and A3002RU 3.0.0-B20230809.1615. This issue affects some unknown processing of the file /boafrm/formIpQoS of the component HTTP POST Request Handler. The manipulation of the argument mac leads to buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow vulnerability in TOTOLINK A3002R/A3002RU routers (firmware 3.0.0-B20230809.1615) in the /boafrm/formIpQoS HTTP POST handler. The 'mac' parameter is not properly bounds-checked, allowing remote attackers to overflow a buffer via crafted POST request.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0.0-b20230809.1615= 3.0.0-b20230809.1615CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label or access the router web interface and look for the model number (A3002R or A3002RU) typically displayed on the status page or footerAffected if The model is TOTOLINK A3002R or A3002RU - other models are not affected
-
Check firmware versionAccess the router web interface, navigate to the status or system settings page, and locate the firmware version field. Compare exactly to '3.0.0-B20230809.1615'Affected if Firmware version equals 3.0.0-B20230809.1615 - versions before or after this may have different vulnerability status
-
Verify web interface is accessibleAttempt to access the router login page via HTTP (port 80) from the WAN IP address if remote management is enabled, or from LAN. The vulnerable endpoint is /boafrm/formIpQoSAffected if The /boafrm/formIpQoS HTTP handler is reachable - this is required for the buffer overflow to be exploitable
-
Check if remote management is enabledLog into the router web interface, go to Advanced Settings or Administration, and check if 'Remote Management' or 'Web Access from WAN' is enabled. Also verify WAN IP accessibility using an external host or online port check toolAffected if Remote management/WAN web access is enabled - this exposes the vulnerable handler to external attackers
You are affected if you have a TOTOLINK A3002R or A3002RU router running exactly firmware version 3.0.0-B20230809.1615 AND the router web interface (specifically the /boafrm/formIpQoS handler) is accessible, especially from the WAN side.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware update when available. Until then, disable remote management interface or restrict access to trusted IPs only.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4733 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data