CVE-2019-0344
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2019-0344 being exploited?
Yes. CVE-2019-0344 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2019-0344?
CVE-2019-0344 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2019-0344?
Yes. A fix has been recorded for CVE-2019-0344. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2019-0344 affect?
CVE-2019-0344 affects sap:commerce_cloud. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 6.4
- affected< 6.5
- affected< 6.6
- affected< 6.7
- affected< 1808
- affected< 1811
- affected< 1905
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 4 Oct 2024 (SSVC 2.0.3).
timeline
- 14 Aug 2019Published
- 30 Sept 2024Added to CISA KEV (exploited in the wild) · 1,873 days (about 5 years) later
- 4 Oct 2024CISA SSVC assessment: exploitation active · 5 days later
- 21 Oct 2024CISA remediation due date (US federal agencies) · 16 days later
- 21 Oct 2025CVE record last updated · 366 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkwiki.scn.sap.com /wiki/pages/viewpage.action?pageId=523998017
- Linklaunchpad.support.sap.com /#/notes/2786035
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-0344
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.