NVD / CVE Program· CNA mitre

CVE-2022-32548: An issue was discovered on certain DrayTek Vigor routers before July 2022 such as the Vigor3910 before 4.3.1.1.

Noroxi assessment

Priority: Plan (action score 49/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 33.9% (FIRST EPSS); higher than 98.3% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue was discovered on certain DrayTek Vigor routers before July 2022 such as the Vigor3910 before 4.3.1.1. /cgi-bin/wlogin.cgi has a buffer overflow via the username or password to the aa or ab field.

CriticalCVSS 9.8 · v3.1—Proof of concept No fix recorded

BDU:2022-04804

Published: Aug 29, 2022
Updated: Jun 17, 2026
EPSS: 33.9% · 98th percentile
CWE: CWE-120

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 10 / 30 · 33.9%

CNA vs NVD score

NVD: 9.8
CNA · mitre: 10.0; 0.2 point gap

CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:C/UI:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
draytek	vigor2133vac	cpe:2.3:h:draytek:vigor2133vac
draytek	vigor3910 firmware	cpe:2.3:o:draytek:vigor3910_firmware
draytek	vigor3910	cpe:2.3:h:draytek:vigor3910
draytek	vigor1000b firmware	cpe:2.3:o:draytek:vigor1000b_firmware
draytek	vigor1000b	cpe:2.3:h:draytek:vigor1000b
draytek	vigor2962 firmware	cpe:2.3:o:draytek:vigor2962_firmware
draytek	vigor2962	cpe:2.3:h:draytek:vigor2962
draytek	vigor2962p firmware	cpe:2.3:o:draytek:vigor2962p_firmware
draytek	vigor2962p	cpe:2.3:h:draytek:vigor2962p
draytek	vigor2927 firmware	cpe:2.3:o:draytek:vigor2927_firmware
draytek	vigor2927	cpe:2.3:h:draytek:vigor2927
draytek	vigor2927ax firmware	cpe:2.3:o:draytek:vigor2927ax_firmware

and 124 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

draytek vigor1000b firmwarebefore 4.3.1.1
draytek vigor165 firmwarebefore 4.2.4
draytek vigor166 firmwarebefore 4.2.4
draytek vigor2133 firmwarebefore 3.9.6.4
draytek vigor2133ac firmwarebefore 3.9.6.4
draytek vigor2133fvac firmwarebefore 3.9.6.4
draytek vigor2133n firmwarebefore 3.9.6.4
draytek vigor2133vac firmwarebefore 3.9.6.4
draytek vigor2135 firmwarebefore 4.4.2
draytek vigor2135ac firmwarebefore 4.4.2
draytek vigor2135fvac firmwarebefore 4.4.2
draytek vigor2135vac firmwarebefore 4.4.2
draytek vigor2620l firmwarebefore 3.9.8.1
draytek vigor2620ln firmwarebefore 3.9.8.1
draytek vigor2762 firmwarebefore 3.9.6.4
draytek vigor2762ac firmwarebefore 3.9.6.4
draytek vigor2762n firmwarebefore 3.9.6.4
draytek vigor2762vac firmwarebefore 3.9.6.4
draytek vigor2765 firmwarebefore 4.4.2
draytek vigor2765ac firmwarebefore 4.4.2

Same product

draytek: all records

Other highest-scoring records for the same primary product.

CVE-2024-41589DrayTek Vigor310 devices through 4.3.2.6 use unencrypted HTTP for authentication requests.
35Monitor
CVE-2024-41595DrayTek Vigor310 devices through 4.3.2.6 allow a remote attacker to change settings or cause a denial of service via .cgi pages because of m
32Monitor
CVE-2024-41586A stack-based Buffer Overflow vulnerability in DrayTek Vigor310 devices through 4.3.2.6 allows a remote attacker to execute arbitrary code v
32Monitor

Published before and after this one in the same product

Later →CVE-2024-23721Mar 20, 2024 · A Directory Traversal issue was discovered in process_post on Draytek Vigor3910 4.3.2.5 devices.
30Monitor
Later →CVE-2024-46550Sep 18, 2024 · Draytek Vigor 3910 v4.3.2.6 was discovered to contain a buffer overflow in the CGIbyFieldName parameter at chglog.cgi.
30Monitor
Later →CVE-2024-46551Sep 18, 2024 · Draytek Vigor 3910 v4.3.2.6 was discovered to contain a buffer overflow in the sBPA_Pwd parameter at inet15.cgi.
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:8	2023-10-27

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedAug 29, 2022
First PoCOct 27, 2023+424 d
TodayNov 1, 2026+1526 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records