LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6522: Information Disclosure in ExtremePacs's Extreme XDS

Incorrect Use of Privileged APIs vulnerability in ExtremePacs Extreme XDS allows Collect Data as Provided by Users. This issue affects Extreme XDS: before 3914.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-6522 is a high-severity flaw in ExtremePacs Extreme XDS before version 3914. A remote, unauthenticated attacker may be able to collect user-provided data and affect limited confidentiality and integrity. The public record is sparse, so prioritize confirming whether Extreme XDS is deployed and internet-accessible.

Executive priority

Treat this as a near-term remediation item if Extreme XDS is in use. The risk is elevated because the vulnerability is network-accessible and unauthenticated, but public evidence does not show known exploitation. Focus first on internet-facing or sensitive-data environments.

Technical view

The CVE describes incorrect use of privileged APIs, mapped to CWE-648, in Extreme XDS before 3914. CVSS 3.1 is 7.2: network attack vector, low complexity, no privileges, no user interaction, scope changed, low confidentiality and integrity impact, no availability impact.

Likely exposure

Organizations running ExtremePacs Extreme XDS versions before 3914 are potentially exposed, especially if the system is reachable over untrusted networks. The source bundle does not identify specific deployment configurations, modules, or default exposure paths.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not listed as KEV in the bundle. The CVSS vector indicates the issue is remotely reachable without authentication or user interaction, but public exploit details are not provided here.

Researcher notes

Public technical detail is limited. The CVE record names incorrect use of privileged APIs and user-provided data collection, but does not describe precise endpoints, prerequisites, or exploit mechanics. One listed USOM link is marked broken in the bundle; use the available Turkish government advisory and CVE records for confirmation.

Mitigation direction

  • Inventory ExtremePacs Extreme XDS deployments and record versions.
  • Upgrade affected Extreme XDS instances to version 3914 or later where supported.
  • Review the Turkish government advisory for any vendor-specific instructions.
  • Restrict network access to Extreme XDS until remediation is complete.
  • Monitor vendor and government advisories for updated guidance.

Validation and detection

  • Confirm whether Extreme XDS is installed in the environment.
  • Compare installed versions against the affected range: before 3914.
  • Verify external and internal network exposure for Extreme XDS services.
  • Confirm remediation by documenting version 3914 or later.
  • Review logs for unusual data access around exposed systems.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-648: 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 lookup
cve · low confidence lookup

CVE-2023-6522 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2023-6522Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ExtremePacsExtreme XDS0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-648 · source CWE mapping

Incorrect Use of Privileged APIs

Incorrect Use of Privileged APIs represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.