First published: Fri Dec 31 2004(Updated: )
Unspecified vulnerability in Journalness 3.0.7 and earlier allows remote attackers to create or modify posts via unknown attack vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Journalness | =2.1.1 | |
Journalness | =1.11 | |
Journalness | =3.0.0 | |
Journalness | =3.0.3 | |
Journalness | =2.1.2 | |
Journalness | =2.1.4 | |
Journalness | =3.0.1 | |
Journalness | =2.1 | |
Journalness | =1.12_r1 | |
Journalness | =3.0.4 | |
Journalness | =3.0.5 | |
Journalness | =3.0.7 | |
Journalness | =1.12 | |
Journalness | =1.13_r1 | |
Journalness | =1.13 | |
Journalness | =3.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2004-2639 is considered high due to its potential for remote attacks allowing unauthorized modifications.
To fix CVE-2004-2639, you should upgrade to Journalness version 3.0.8 or later where the vulnerability has been addressed.
CVE-2004-2639 affects Journalness versions 3.0.7 and earlier, including various earlier releases such as 2.x and 1.x.
CVE-2004-2639 may allow remote attackers to create or modify posts without authorization.
There is no specific public exploit detailed for CVE-2004-2639, but the vulnerability poses significant risk due to its remote nature.