← Back to results
Vulnerability record · public intelligence
CVE-2007-3676
UNKNOWN

CVE-2007-3676

Published Feb 12, 2008 · Updated Oct 23, 2026

Severity · CVSSUNKNOWN · 10.0
Known exploitationNot listed
EPSS / likelihood4.33%
QFinch risk score20 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

IBM DB2 Universal Database (UDB) Administration Server (DAS) 8 before Fix Pack 16 and 9 before Fix Pack 4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via modified pointer values in unspecified remote administration requests, which triggers memory corruption or other invalid memory access. NOTE: this might be the same issue as CVE-2008-0698.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

IBM DB2 Universal Database (UDB) Administration Server (DAS) 8 before Fix Pack 16 and 9 before Fix Pack 4 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via modified pointer values in unspecified remote administration requests, which triggers memory corruption or other invalid memory access. NOTE: this might be the same issue as CVE-2008-0698.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
20%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. 1019318 ↗
  2. 20080207 IBM DB2 Universal Database Administration Server Memory Corruption Vulnerability ↗

Record history

Published Feb 12, 2008 · Last refreshed Oct 23, 2026