LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21555: Vulnerability in the MySQL Shell for VS Code product of Oracle MySQL (component: Shell: GUI).

Vulnerability in the MySQL Shell for VS Code product of Oracle MySQL (component: Shell: GUI). Supported versions that are affected are 1.1.8 and prior. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Shell for VS Code executes to compromise MySQL Shell for VS Code. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Shell for VS Code, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Shell for VS Code accessible data as well as unauthorized read access to a subset of MySQL Shell for VS Code accessible data. CVSS 3.1 Base Score 4.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N).

MediumCVSS 4.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-21555 affects Oracle MySQL Shell for VS Code 1.1.8 and earlier. An attacker already logged into the same infrastructure with high privileges could, with another user's interaction, read or change some data accessible through the tool. Business impact is limited but relevant where privileged database tooling is used on shared or sensitive workstations.

Executive priority

Treat as a targeted workstation and administration-tool risk, not an internet-wide emergency. Prioritize remediation where privileged users manage sensitive MySQL data or use shared infrastructure.

Technical view

The source describes a local, low-complexity issue in MySQL Shell for VS Code Shell GUI with high privileges and required user interaction. CVSS is 4.2, with low confidentiality and integrity impact, no availability impact, and scope change, meaning effects may extend beyond the vulnerable component.

Likely exposure

Exposure is most likely on developer, DBA, or operations systems running MySQL Shell for VS Code 1.1.8 or earlier, especially where multiple privileged users access shared infrastructure.

Exploitation context

The source bundle does not identify active exploitation, and CISA KEV status is false. Exploitation requires local infrastructure logon, high privileges, and human interaction from another person.

Researcher notes

The source names MySQL Shell for VS Code and component Shell: GUI, but the affected product field lists MySQL Server. The bundle provides no CWE, root-cause detail, exploit evidence, or fixed version, so validation should anchor on Oracle's advisory and local version inventory.

Mitigation direction

  • Inventory MySQL Shell for VS Code installations and identify versions 1.1.8 or earlier.
  • Review Oracle's July 2022 Critical Patch Update guidance for the vendor-supported fix.
  • Upgrade or remove affected installations according to Oracle guidance.
  • Restrict privileged local logon access on systems running database administration tooling.
  • Avoid shared privileged workstations for database management workflows.

Validation and detection

  • Confirm installed MySQL Shell for VS Code versions across developer and DBA endpoints.
  • Verify affected instances have been upgraded or removed per Oracle guidance.
  • Check whether privileged local access is limited to approved administrators.
  • Confirm users understand prompts or interactions involving database tooling on shared infrastructure.
Prepared
Confidence
medium
Sources
3

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.

cve · low confidence lookup

CVE-2022-21555 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
Medium
CVSS
4.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/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
0Timeline events
0ADP providers
2Source links

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
4.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N1.12.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.2Medium
CVSS 3.1 vector shape for CVE-2022-21555Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Server1.1.8 and priorListed
Weakness

CWE details

No CWE listed

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