What is CVE-2004-1367?A medium-severity flaw in Application Server, explained.
CVE-2004-1367 is a medium-severity flaw (CVSS 4.4) in Application Server from Oracle, published on 4 August 2004. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 7.3%. If you run an affected version, plan in the vendor’s fix.
Published 4 August 2004. Record last updated 16 June 2026. We keep this page's data up to date.
What is CVE-2004-1367? In plain terms.
An attacker has to be already on the device without logging in. If it works, the attacker can read some data, change some data and slow it down.
Oracle 10g Database Server, when installed with a password that contains an exclamation point ("!") for the (1) DBSNMP or (2) SYSMAN user, generates an error that logs the password in the world-readable postDBCreation.log file, which could allow local users to obtain that password and use it against SYS or SYSTEM accounts, which may have been installed with the same password.
What kind of flaw is it?
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offSome conditions needed
- Login needed firstNo login needed
- What an attacker getsCan read some data, change some data and slow it down
Severity vector: AV:L/AC:M/Au:N/C:P/I:P/A:P
Is CVE-2004-1367 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 7.3%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2004-1367 scores 14. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2004-1367 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2004-1367? 9 products.
The published record lists 9 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Application Server
by Oracle
Affected versionsall versions9.0.29.0.2.0.09.0.2.0.19.0.2.19.0.2.29.0.2.39.0.39.0.3.19.0.49.0.4.09.0.4.1 - Application
Oracle9i
by Oracle
Affected versionsclient_9.2.0.1client_9.2.0.2enterprise_8.1.7enterprise_9.0.1enterprise_9.0.1.4enterprise_9.0.1.5 - Application
Oracle8i
by Oracle
Affected versionsenterprise_8.0.5_.0.0enterprise_8.0.6_.0.0enterprise_8.0.6_.0.1enterprise_8.1.5_.0.0enterprise_8.1.5_.0.2enterprise_8.1.5_.1.0 - Application
E-Business Suite
by Oracle
Affected versions11.5.111.5.211.5.311.5.411.5.511.5.6 - Application
Oracle10g
by Oracle
Affected versionsenterprise_9.0.4_.0enterprise_10.1.0.2personal_9.0.4_.0personal_10.1_.0.2standard_9.0.4_.0standard_10.1_.0.2 - Application
Enterprise Manager
by Oracle
Affected versions99.0.1 - Application
Collaboration Suite
by Oracle
Affected versionsrelease_1 - Application
Enterprise Manager Database Control
by Oracle
Affected versions10.1.2 - Application
Enterprise Manager Grid Control
by Oracle
Affected versions10.1.0.2
How do I fix CVE-2004-1367? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2004-1367 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Oracle 10g Database Server, when installed with a password that contains an exclamation point ("!") for the (1) DBSNMP or (2) SYSMAN user, generates an error...
- Matched to
- Application Server on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2004-1367 is a medium-severity flaw in Application Server from Oracle, published on 4 August 2004. An attacker has to be already on the device without logging in. If it works, the attacker can read some data, change some data and slow it down.
It scores 4.4 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2004-1367 is 14 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 7.3%. That can change at any time, which is why we keep watching.
For Application Server from Oracle: all versions, 9.0.2, 9.0.2.0.0, 9.0.2.0.1, 9.0.2.1, 9.0.2.2 and 6 more. The record lists 9 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.