CVE-2008-0307
First published: Tue Mar 11 2008(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| SAP MaxDB | =7.6.0.37 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://labs.idefense.com/intelligence/vulnerabilities/display.php?id=669
- http://www.securityfocus.com/bid/28183
- http://www.securitytracker.com/id?1019571
- http://secunia.com/advisories/29312
- http://www.vupen.com/english/advisories/2008/0844/references
- https://exchange.xforce.ibmcloud.com/vulnerabilities/41107
Frequently Asked Questions
What is the severity of CVE-2008-0307?
CVE-2008-0307 is classified as a critical vulnerability allowing remote code execution.
How do I fix CVE-2008-0307?
To fix CVE-2008-0307, upgrade SAP MaxDB to version 7.6.0.38 or later.
What causes the vulnerability CVE-2008-0307?
CVE-2008-0307 is caused by an integer signedness error that leads to heap corruption.
Who is affected by CVE-2008-0307?
CVE-2008-0307 affects users of SAP MaxDB version 7.6.0.37 and possibly earlier versions.
Can CVE-2008-0307 be exploited remotely?
Yes, CVE-2008-0307 can be exploited by remote attackers to execute arbitrary code.
- collector/nvd-historical
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/severity
- agent/weakness
- agent/description
- agent/tags
- agent/event
- agent/first-publish-date
- agent/source
- vendor/sap
- canonical/sap maxdb
- version/sap maxdb/7.6.0.37