CVE-2008-6869: Oramon Oracle Database Monitoring Tool 2.0.1 stores sensitive information under the web root with insufficient

This month

MEDIUM 5.0DOWNGRADE

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

Oramon Oracle Database Monitoring Tool 2.0.1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database containing credentials via a direct request for config/oramon.ini.

Why this priority

EPSS top 6%: 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	6.2% (top 6%)
CISA exploited list	No
Weakness	CWE-264
Published	2009-07-23
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: oramon

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

Am I affected?

Timeline

2009-07-23 19:30 UTCPublished CVE record published
2026-06-16 23:03 UTCUpdated Record last modified

oramon oramon DOWNGRADE

Affected: 2.0.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.1

1. Check installed version

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

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

apt-cache madison oramon sudo apt install oramon=<VERSION_BEFORE_2.0.1> sudo apt-mark hold oramon

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

dnf --showduplicates list oramon sudo dnf downgrade oramon-<VERSION_BEFORE_2.0.1> sudo dnf versionlock add oramon

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: OraMon 2.0.1 - Remote Configuration 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-2008-6869?

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

Is CVE-2008-6869 being exploited?

CVE-2008-6869 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-6869 affect?

CVE-2008-6869 affects oramon. Severity is medium (CVSS 5.0). Oramon Oracle Database Monitoring Tool 2.0.1 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database containing credentials via a direct request for config/oramo

How urgent is CVE-2008-6869?

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

Software pages

Oracle Database vulnerabilities

References

← Back to latest CVEs