CVE-2023-33778Public exploitNetwork attack vector

Device ownership hijacking via forged registration URLs

Published Jun 1, 2023 · Updated Jan 9, 2025

Hard-coded keys in affected DrayTek Vigor and MyVigor releases allow remote attackers to bind devices to attacker-controlled accounts. The registration flow accepts AES-CBC verification ciphertext made with a key derived predictably from the model and MAC address plus fixed padding. An attacker-controlled MyVigor account and a known or brute-forced target MAC address are sufficient against router firmware before 3.9.6 or 4.2.4, access-point firmware before 1.4.0, switch firmware before 2.6.7, and MyVigor before 2.3.2; binding blocks the owner and enables WCF and DrayDDNS license creation and synchronization.

CVSS severity9.8
Critical
EPSS probability0.59%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded keys in affected DrayTek Vigor and MyVigor releases allow remote attackers to bind devices to attacker-controlled accounts. The registration flow accepts AES-CBC verification ciphertext made with a key derived predictably from the model and MAC address plus fixed padding. An attacker-controlled MyVigor account and a known or brute-forced target MAC address are sufficient against router firmware before 3.9.6 or 4.2.4, access-point firmware before 1.4.0, switch firmware before 2.6.7, and MyVigor before 2.3.2; binding blocks the owner and enables WCF and DrayDDNS license creation and synchronization.

The record

CVE
CVE-2023-33778
Published
Jun 1, 2023
Updated
Jan 9, 2025
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-321, CWE-798
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 1, 2023CVE publishedPublication date reported by the CVE source.
  2. Jan 9, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

9.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
CWE-798Use of Hard-coded Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo