Security readout for executives and security teams
Plain-English summary
CVE-2023-22844 is an authentication bypass in Milesight VPN v2.0.2. A remote attacker could send a crafted network request that bypasses token verification, potentially gaining limited confidentiality, integrity, and availability impact without credentials or user interaction.
Executive priority
Treat this as a high-priority exposure review for any Milesight VPN deployment. Urgency is strongest where v2.0.2 is externally reachable, because authentication bypass can undermine trust in the VPN boundary.
Technical view
The issue is in requestHandlers.js verifyToken functionality in Milesight VPN v2.0.2. The CVE maps to CWE-321 and has CVSS 3.1 score 7.3, with network attack vector, low complexity, no privileges required, and low C/I/A impact.
Likely exposure
Organizations are exposed if they run Milesight VPN v2.0.2, especially when the service is reachable from untrusted networks. The provided sources do not identify other affected versions or products.
Exploitation context
The CVE describes exploitation via a specially crafted network request. It is not listed in KEV, and the provided sources do not state active exploitation or public weaponization.
Researcher notes
Evidence supports a network-reachable authentication bypass in verifyToken, but the bundle does not provide exploit details, patch status, or affected-version range beyond v2.0.2. Avoid assuming broader Milesight exposure without vendor confirmation.
Mitigation direction
- Inventory Milesight VPN deployments and identify any v2.0.2 instances.
- Restrict service access to trusted networks until vendor guidance is confirmed.
- Check Milesight or Talos guidance for fixed versions or official mitigations.
- Prioritize replacement, upgrade, or compensating controls where v2.0.2 remains reachable.
Validation and detection
- Confirm product and version from asset inventory or administrative records.
- Review firewall and exposure data for internet-reachable Milesight VPN services.
- Check authentication logs for unusual unauthenticated or failed token activity.
- Verify whether vendor remediation has been applied once guidance is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-321: 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.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-22844 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.