LiveActive security incident?Get immediate response
CVE Record

CVE-2019-0344: Due to unsafe deserialization used in SAP Commerce Cloud (virtualjdbc extension), versions 6.4, 6.5, 6.6, 6...

Due to unsafe deserialization used in SAP Commerce Cloud (virtualjdbc extension), versions 6.4, 6.5, 6.6, 6.7, 1808, 1811, 1905, it is possible to execute arbitrary code on a target machine with 'Hybris' user rights, resulting in Code Injection.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw lets an unauthenticated network attacker potentially run code on affected SAP Commerce Cloud systems through unsafe deserialization in the virtualjdbc extension. Successful exploitation runs with Hybris user rights and can compromise confidentiality, integrity, and availability.

Executive priority

Treat this as urgent. The issue is critical, remotely reachable without credentials, and listed by CISA as known exploited. Prioritize systems supporting revenue, customer data, or internet-facing commerce operations.

Technical view

CVE-2019-0344 is CWE-502 unsafe deserialization in SAP Commerce Cloud virtualjdbc extension. The provided CVSS 3.1 vector is 9.8, network-accessible, low complexity, no privileges, no user interaction, unchanged scope, with high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely where SAP Commerce Cloud or Hybris deployments run affected listed versions with the virtualjdbc extension present or reachable. Internet-facing or broadly reachable commerce environments carry the highest operational risk.

Exploitation context

CISA lists CVE-2019-0344 in the Known Exploited Vulnerabilities catalog, which supports known exploitation. The bundle does not provide exploit details, affected deployment prevalence, or proof-of-concept status.

Researcher notes

Evidence supports critical remote code execution via unsafe deserialization in the virtualjdbc extension with Hybris user rights. Version wording in the bundle should be verified against SAP Note 2786035 because the affected-version notation is incomplete and potentially ambiguous.

Mitigation direction

  • Review SAP Note 2786035 and apply vendor-directed remediation.
  • Confirm SAP Commerce Cloud versions and virtualjdbc extension status.
  • Prioritize externally reachable or business-critical commerce systems first.
  • Limit network reachability to affected services during remediation planning.
  • Retire or isolate systems that cannot receive vendor-supported fixes.

Validation and detection

  • Inventory SAP Commerce Cloud and Hybris deployments.
  • Check whether virtualjdbc extension is installed, enabled, or reachable.
  • Map deployments to listed affected versions: 6.4 through 1905.
  • Confirm remediation status against SAP Note 2786035.
  • Review logs for suspicious activity on affected systems.
Prepared
Confidence
high
Sources
5

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

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-0344 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
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

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

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
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2019-0344Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
SAP SESAP Commerce Cloud (virtualjdbc extension)< 6.4, < 6.5, < 6.6, < 6.7, < 1808, < 1811, < 1905Listed
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.