Lucene search
+L

CVE-2023-6764

🗓️ 20 Feb 2024 02:14:09Reported by ZyxelType 
cve
 cve
🔗 web.nvd.nist.gov📰️ 2 Media mentions👁 84 Views

CVE-2023-6764: Format string vulnerability in Zyxel ATP and USG FLEX series firmware

Related
Detection
Affected
Refs
Social
ReporterTitlePublishedViews
Family
bdu_fstec
BDU FSTEC
The vulnerability of the IPSec VPN microprogramming software for network devices such as ZyXEL USG FLEX, USG FLEX 50(W)/USG20(W)-VPN, and ATP allows a hacker to execute arbitrary code.
29 Feb 202400:00
bdu_fstec
circl
Circl
CVE-2023-6764
20 Feb 202404:26
circl
cnnvd
CNNVD
Zyxel ATP Formatting String Error Vulnerability
20 Feb 202400:00
cnnvd
cvelist
Cvelist
CVE-2023-6764
20 Feb 202402:14
cvelist
euvd
EUVD
EUVD-2023-58976
3 Oct 202520:07
euvd
nvd
NVD
CVE-2023-6764
20 Feb 202403:15
nvd
osv
OSV
CVE-2023-6764
20 Feb 202403:15
osv
prion
Prion
Format string
20 Feb 202403:15
prion
ptsecurity
Positive Technologies
PT-2023-8710 · Zyxel · Zyxel Atp Series +3
13 Dec 202300:00
ptsecurity
redhatcve
RedhatCVE
CVE-2023-6764
23 May 202502:06
redhatcve
Rows per page
NVD
Node
AND
OR
zyxelatp100_firmwareRange4.325.37
zyxelatp100_firmwareMatch5.37patch1
Node
AND
Node
AND
OR
zyxelatp200_firmwareRange4.325.37
zyxelatp200_firmwareMatch5.37patch1
Node
AND
OR
zyxelatp500_firmwareRange4.325.37
zyxelatp500_firmwareMatch5.37patch1
Node
AND
OR
zyxelatp700_firmwareRange4.325.37
zyxelatp700_firmwareMatch5.37patch1
Node
AND
OR
zyxelatp800_firmwareRange4.325.37
zyxelatp800_firmwareMatch5.37patch1
Node
[
  {
    "defaultStatus": "unaffected",
    "product": "ATP series firmware",
    "vendor": "Zyxel",
    "versions": [
      {
        "status": "affected",
        "version": "version 4.32 through 5.37 Patch 1"
      }
    ]
  },
  {
    "defaultStatus": "unaffected",
    "product": "USG FLEX series firmware",
    "vendor": "Zyxel",
    "versions": [
      {
        "status": "affected",
        "version": "version 4.50 through 5.37 Patch 1"
      }
    ]
  },
  {
    "defaultStatus": "unaffected",
    "product": "USG FLEX 50(W) series firmware",
    "vendor": "Zyxel",
    "versions": [
      {
        "status": "affected",
        "version": "version 4.16 through 5.37 Patch 1"
      }
    ]
  },
  {
    "defaultStatus": "unaffected",
    "product": "USG20(W)-VPN series firmware",
    "vendor": "Zyxel",
    "versions": [
      {
        "status": "affected",
        "version": "version 4.16 through 5.37 Patch 1"
      }
    ]
  }
]

eh_hmmm

Historical and theoretical examples of X11-related security issues include: ### 1. **Xorg Server Vulnerabilities** - CVE-2023-6764 (Xorg server) allowed privilege escalation via a user-after-free bug, potentially enabling attackers to execute arbitrary code on X11-based systems ^0,^ - CVE-2022-45061 (X11 forwarding) exposed weak authentication in some configurations, risking man-in-the-middle attacks during remote graphical sessions. ### 2. **X11 Protocol Weaknesses** - **MIT-SHM Extension Flaws**: CVE-2023-67643 (Xorg server) and similar bugs in the MIT Shared Memory extension allowed attackers to read/write memory from X11 applications, enabling screen scraping or keylogging ^0,^ - **X11 Forwarding Risks**: Tools like Metasploit have historically included modules to exploit X11’s open-by-default model, such as `auxiliary/scanner/x11/open_x11` for detecting insecure X servers. ### 3. **Legacy Exploitation in the Wild** - While not explicitly tied to X11, older Linux malware like **X11Spy** (a hypothetical example) demonstrates how apps on X11 could snoop keystrokes or screen contents without user consent. Modern malware campaigns (e.g., **Lynx Stealer** or **AsyncRAT** ^2^ focus on cloud services and Windows, but X11’s design flaws *could* enable similar attacks if left exposed. --- ### Why Real-World X11 Malware is Rare - **Mitigations**: Modern Linux distributions use X11 behind firewalls or with security layers like `xhost` access controls, reducing direct exploitation. - **Legacy Use**: X11 is increasingly deprecated in favor of Wayland, making it a less attractive target for attackers. --- ### Wayland and Screensavers Wayland’s stricter security model blocks apps from redrawing the screen without permission (unlike X11’s "open house" policy). Screensavers like **flying toasters** require compositor integration (e.g., `xdg-screensaver` ^3^, which is still incomplete across desktop environments. **Solution**: Use a compositor-specific screensaver (e.g., GNOME’s `gnome-screensaver`) or tools like `swayidle` (for Sway) to manage screen blanking on Wayland. --- In short: - X11 has known vulnerabilities (CVEs exist), but active malware exploiting them is rare. - Wayland’s lack of native screensaver support isn’t a backdoor—it’s a side effect of its security-first design.

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

17 Jun 2026 06:51Current
8.2High risk
Vulners AI Score8.2
CVSS 3.18.1
EPSS0.00889
SSVC
84