CVE-2008-0307: Integer signedness error in vserver in SAP MaxDB 7.6.0.37, and possibly other versions, allows remote attacker

This month

HIGH 9.3DOWNGRADE

CVE-2008-0307 is a high-severity flaw (CVSS 9.3) affecting maxdb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 9%: very likely to be exploited

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.3 (High)
EPSS exploit chance	4.0% (top 9%)
CISA exploited list	No
Weakness	CWE-189
Published	2008-03-11
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: sap

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2008-03-11 23:44 UTCPublished CVE record published
2026-06-16 22:49 UTCUpdated Record last modified

sap maxdb DOWNGRADE

Affected: 7.6.0.37

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.6.0.37

1. Check installed version

apt-cache policy maxdb || rpm -q maxdb || maxdb --version

2. No fixed release: DOWNGRADE to a release before 7.6.0.37 (Debian / Ubuntu)

apt-cache madison maxdb sudo apt install maxdb=<VERSION_BEFORE_7.6.0.37> sudo apt-mark hold maxdb

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list maxdb sudo dnf downgrade maxdb-<VERSION_BEFORE_7.6.0.37> sudo dnf versionlock add maxdb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2008-0307?

maxdb: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2008-0307 being exploited?

CVE-2008-0307 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2008-0307 affect?

CVE-2008-0307 affects maxdb. Severity is high (CVSS 9.3). 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.

How urgent is CVE-2008-0307?

Priority 55/100. Critical severity; EPSS top 9%: very likely to be exploited

Software pages

SAP vulnerabilities

Related CVEs

CVE-2018-2450 HIGH 7.2 DOWNGRADE SAP MaxDB (liveCache), versions 7.8 and 7.9, allows an attacker who gets DBM operator privileges to execute cr
CVE-2015-2282 HIGH 7.5 MITIGATE DOWNGRADE Stack-based buffer overflow in the LZC decompression implementation (CsObjectInt::CsDecomprLZC function in vpa
CVE-2015-2278 MEDIUM 5.0 MITIGATE DOWNGRADE The LZH decompression implementation (CsObjectInt::BuildHufTree function in vpa108csulzh.cpp) in SAP MaxDB 7.5
CVE-2010-1185 HIGH 10.0 DOWNGRADE 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 attac
CVE-2008-1810 MEDIUM 4.4 DOWNGRADE Untrusted search path vulnerability in dbmsrv in SAP MaxDB 7.6.03.15 on Linux allows local users to gain privi

References

← Back to latest CVEs