CVE-2008-0244

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 80.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 80%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 80%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2008 — isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

SAP MaxDB 7.6.03 build 007 and earlier allows remote attackers to execute arbitrary commands via "&&" and other shell metacharacters in exec_sdbinfo and other unspecified commands, which are executed when MaxDB invokes cons.exe.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
82
EG Risk 82/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation80% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2008. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
80%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix has been recorded since the CVE record was published in 2008. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

January 12, 2008

Last Modified

April 23, 2026

References (9)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 22 repeat rows among the latest 74 are merged into the row they repeat.

  1. 2026-10-09 20:00 UTCEPSS rescoreEPSS 80% · 99th percentile
  2. 2026-10-07 23:37 UTCEPSS rescoreEPSS 80% · 99th percentile
  3. 2026-10-06 15:09 UTCEPSS rescoreEPSS 80% · 99th percentile
  4. 2026-10-03 14:20 UTCEPSS rescoreEPSS 80% · 99th percentile
  5. 2026-10-01 19:42 UTCEPSS rescoreEPSS 80% · 99th percentile
  6. 2026-09-29 07:46 UTCEG score recompute
  7. 2026-09-18 19:20 UTCEPSS rescoreEPSS 80% · 99th percentile
  8. 2026-09-17 19:20 UTCEPSS rescoreEPSS 80% · 99th percentile
  9. 2026-09-15 03:04 UTCEPSS rescoreEPSS 80% · 99th percentile
  10. 2026-09-05 15:22 UTCEPSS rescoreEPSS 80% · 99th percentile
  11. 2026-07-26 13:34 UTCEG score recompute▲ 10.00
  12. 2026-07-25 14:12 UTCEPSS rescoreEPSS 80% · 99th percentile
  13. 2026-07-24 14:11 UTCEPSS rescoreEPSS 80% · 99th percentile
  14. 2026-07-23 00:55 UTCEG score recompute
  15. 2026-07-23 00:34 UTCEG score recompute▼ 8.20
  16. 2026-07-23 00:00 UTCEG score recompute▲ 8.20
  17. 2026-07-22 21:39 UTCEG score recompute▼ 9.00
  18. 2026-07-22 14:03 UTCEPSS rescoreEPSS 80% · 99th percentile
  19. 2026-07-21 15:19 UTCEPSS rescoreEPSS 80% · 99th percentile
  20. 2026-07-20 17:03 UTCEPSS rescoreEPSS 80% · 99th percentile
  21. 2026-07-16 16:58 UTCEPSS rescoreEPSS 80% · 99th percentile
  22. 2026-07-15 16:54 UTCEPSS rescoreEPSS 80% · 99th percentile
  23. 2026-07-13 06:07 UTCEPSS rescoreEPSS 80% · 99th percentile
  24. 2026-07-06 02:19 UTCEPSS rescoreEPSS 80% · 99th percentile
  25. 2026-07-02 14:00 UTCEPSS rescoreEPSS 80% · 99th percentile
Show 27 more
  1. 2026-07-01 15:02 UTCEPSS rescoreEPSS 80% · 99th percentile
  2. 2026-06-27 03:04 UTCEPSS rescoreEPSS 80% · 99th percentile
  3. 2026-06-25 13:46 UTCEPSS rescoreEPSS 80% · 99th percentile
  4. 2026-06-24 14:02 UTCEPSS rescoreEPSS 80% · 99th percentile
  5. 2026-06-23 21:29 UTCEPSS rescoreEPSS 80% · 99th percentile
  6. 2026-06-21 01:56 UTCEPSS rescoreEPSS 80% · 99th percentile
  7. 2026-06-17 17:49 UTCEPSS rescoreEPSS 80% · 99th percentile
  8. 2026-06-16 17:49 UTCEPSS rescoreEPSS 80% · 99th percentile
  9. 2026-06-15 17:44 UTCEPSS rescoreEPSS 80% · 99th percentile
  10. 2026-06-13 22:57 UTCEPSS rescoreEPSS 90% · 99th percentile
  11. 2026-06-12 23:08 UTCEPSS rescoreEPSS 90% · 99th percentile
  12. 2026-06-10 22:14 UTCEPSS rescoreEPSS 90% · 99th percentile
  13. 2026-06-10 13:17 UTCEPSS rescoreEPSS 90% · 99th percentile
  14. 2026-06-08 14:13 UTCEPSS rescoreEPSS 90% · 99th percentile
  15. 2026-06-05 22:44 UTCEPSS rescoreEPSS 90% · 99th percentile
  16. 2026-06-04 13:09 UTCEPSS rescoreEPSS 90% · 99th percentile
  17. 2026-06-02 20:10 UTCEPSS rescoreEPSS 90% · 99th percentile
  18. 2026-06-01 13:49 UTCEPSS rescoreEPSS 90% · 99th percentile
  19. 2026-05-31 22:28 UTCEPSS rescoreEPSS 90% · 99th percentile
  20. 2026-05-30 23:24 UTCEG score recompute
  21. 2026-05-30 23:24 UTCGHSA enrichmentGHSA-m8c7-xxh7-qrh7 · GitHub severity HIGH
  22. 2026-05-29 13:40 UTCEPSS rescoreEPSS 90% · 99th percentile
  23. 2026-05-28 13:42 UTCEPSS rescoreEPSS 90% · 99th percentile
  24. 2026-05-27 13:37 UTCEPSS rescoreEPSS 90% · 99th percentile
  25. 2026-05-24 16:42 UTCEPSS rescoreEPSS 90% · 99th percentile
  26. 2026-05-20 22:36 UTCEPSS rescoreEPSS 90% · 99th percentile
  27. 2026-05-18 21:29 UTCEPSS rescoreEPSS 90% · 99th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry). No fix is on record, so defenders should restrict or isolate affected systems accordingly.

  • Metasploitauxiliary/admin/maxdb/maxdb_cons_exec✓ verified
    Published Jan 20, 2008

    SAP MaxDB cons.exe Remote Command Injection

    Open source ↗
  • Exploit-DBEDB-4877✓ verified
    Published Jan 9, 2008

    SAP MaxDB 7.6.03.07 - Remote Command Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2008-0244?
CVE-2008-0244 is a high-severity vulnerability; its CVE record was published on January 12, 2008. SAP MaxDB 7.6.03 build 007 and earlier allows remote attackers to execute arbitrary commands via "&&" and other shell metacharacters in exec_sdbinfo and other unspecified commands, which are executed when MaxDB invokes cons.exe.
When was CVE-2008-0244 made public?
CVE-2008-0244 was made public on January 9, 2008: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on January 12, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-0244 actively exploited?
CVE-2008-0244 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 80% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-0244?
No fix for CVE-2008-0244 has been recorded since its CVE record was published in 2008, and EchelonGraph holds no vendor advisory for it. Isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2008-0244

Explore →

Is Your Infrastructure Affected by CVE-2008-0244?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs