CVE-2002-1483: db4web_c and db4web_c.exe programs in DB4Web 3.4 and 3.6 allow remote attackers to read arbitrary files via an

This week

MEDIUM 5.0DOWNGRADE

CVE-2002-1483 is a medium-severity flaw (CVSS 5.0) affecting db4web. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

db4web_c and db4web_c.exe programs in DB4Web 3.4 and 3.6 allow remote attackers to read arbitrary files via an HTTP request whose argument is a filename of the form (1) C: (drive letter), (2) //absolute/path (double-slash), or (3) .. (dot-dot).

Why this priority

EPSS top 5%: very likely to be exploited
Public exploit reference

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

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	8.5% (top 5%)
CISA exploited list	No
Published	2003-04-22
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: db4web

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

Am I affected?

Timeline

2003-04-22 04:00 UTCPublished CVE record published
2026-06-16 21:59 UTCUpdated Record last modified

db4web db4web DOWNGRADE

Affected: 3.4 · 3.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.4

1. Check installed version

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

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

apt-cache madison db4web sudo apt install db4web=<VERSION_BEFORE_3.4> sudo apt-mark hold db4web

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

dnf --showduplicates list db4web sudo dnf downgrade db4web-<VERSION_BEFORE_3.4> sudo dnf versionlock add db4web

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: DB4Web 3.4/3.6 - File Disclosure

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-2002-1483?

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

Is CVE-2002-1483 being exploited?

CVE-2002-1483 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-2002-1483 affect?

CVE-2002-1483 affects db4web. Severity is medium (CVSS 5.0). db4web_c and db4web_c.exe programs in DB4Web 3.4 and 3.6 allow remote attackers to read arbitrary files via an HTTP request whose argument is a filename of the form (1) C: (drive letter), (2) //absolute/path (double-slash), or (3) .. (dot-d

How urgent is CVE-2002-1483?

Priority 46/100. EPSS top 5%: very likely to be exploited; Public exploit reference

Related CVEs

CVE-2002-1484 CRITICAL 9.8 DOWNGRADE DB4Web server, when configured to use verbose debug messages, allows remote attackers to use DB4Web as a proxy

References

← Back to latest CVEs