Maxdb vulnerabilitiesRanked by how likely they are to be used.

Product8 versions
The short answer

Maxdb is made by SAP. We track 8 published vulnerabilities listed under that exact name, across 8 versions. None of them is on the list of flaws known to be exploited today. SAP lists newer releases under their own names, such as Maxdb Odbc Driver, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Maxdb listed under other names? Yes.

SAP also lists Maxdb under more specific names, such as Maxdb Odbc Driver. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Maxdb vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Maxdb's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Maxdb flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 80%

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

    CVSS10.0Published12 Jan 2008
  2. 15%

    Stack-based buffer overflow in serv.exe in SAP MaxDB 7.4.3.32, and 7.6.0.37 through 7.6.06 allows remote attackers to execute arbitrary code via an invalid length parameter in a handshake packet to TCP port 7210.

    CVSS10.0Published29 Mar 2010
  3. 4.0%

    Integer signedness error in vserver in SAP MaxDB 7.6.0.37, and possibly other versions, allows remote attackers to execute arbitrary code via unknown vectors that trigger heap corruption.

    CVSS9.3Published11 Mar 2008
  4. 3.5%

    Stack-based buffer overflow in the LZC decompression implementation (CsObjectInt::CsDecomprLZC function in vpa106cslzc.cpp) in SAP MaxDB 7.5 and 7.6, Netweaver Application Server ABAP, Netweaver Application Server...

    CVSS7.5Published2 Jun 2015
  5. 2.1%

    The LZH decompression implementation (CsObjectInt::BuildHufTree function in vpa108csulzh.cpp) in SAP MaxDB 7.5 and 7.6, Netweaver Application Server ABAP, Netweaver Application Server Java, Netweaver RFC SDK, GUI,...

    CVSS5.0Published2 Jun 2015
  6. 1.7%

    SAP MaxDB (liveCache), versions 7.8 and 7.9, allows an attacker who gets DBM operator privileges to execute crafted database queries and therefore read, modify or delete sensitive data from database.

    CVSS7.2Published14 Aug 2018
  7. 0.4%

    sdbstarter in SAP MaxDB 7.6.0.37, and possibly other versions, allows local users to execute arbitrary commands by using unspecified environment variables to modify configuration settings.

    CVSS6.9Published11 Mar 2008
  8. 0.3%

    Untrusted search path vulnerability in dbmsrv in SAP MaxDB 7.6.03.15 on Linux allows local users to gain privileges via a modified PATH environment variable.

    CVSS4.4Published1 Aug 2008
Precursor Intelligence

Running Maxdb? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Maxdb, across 8 versions.

None of Maxdb's vulnerabilities is on the list of flaws known to be exploited today.

SAP also lists Maxdb under more specific names, such as Maxdb Odbc Driver. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Maxdb. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.