Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2004-1378: The expat XML parser code, as used in the open source Jabber (jabberd) 1.4.3 and earlier, jadc2s 0.9.0 and ear

39
Routine
MEDIUM 5.0DOWNGRADEDOWNGRADE

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

The expat XML parser code, as used in the open source Jabber (jabberd) 1.4.3 and earlier, jadc2s 0.9.0 and earlier, and possibly other packages, allows remote attackers to cause a denial of service (application crash) via a malformed packet to a socket that accepts XML connections.

Why this priority

  • No elevated risk signals yet

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

Risk facts

CVSS score5.0 (Medium)
EPSS exploit chance2.4% (top 16%)
CISA exploited listNo
Published2004-09-21
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: jabberstudio

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

jabberstudio jabberd DOWNGRADE
Affected: 1.4 · 1.4.1 · 1.4.2 · 1.4.2a · 1.4.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.4
1. Check installed version
apt-cache policy jabberd || rpm -q jabberd || jabberd --version
2. No fixed release: DOWNGRADE to a release before 1.4 (Debian / Ubuntu)
apt-cache madison jabberd sudo apt install jabberd=<VERSION_BEFORE_1.4> sudo apt-mark hold jabberd
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jabberd sudo dnf downgrade jabberd-<VERSION_BEFORE_1.4> sudo dnf versionlock add jabberd
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.
jabberstudio jadc2s DOWNGRADE
Affected: 0.6 · 0.7 · 0.8 · 0.9
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.6
1. Check installed version
apt-cache policy jadc2s || rpm -q jadc2s || jadc2s --version
2. No fixed release: DOWNGRADE to a release before 0.6 (Debian / Ubuntu)
apt-cache madison jadc2s sudo apt install jadc2s=<VERSION_BEFORE_0.6> sudo apt-mark hold jadc2s
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list jadc2s sudo dnf downgrade jadc2s-<VERSION_BEFORE_0.6> sudo dnf versionlock add jadc2s
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.
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-2004-1378?

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

Is CVE-2004-1378 being exploited?

CVE-2004-1378 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-2004-1378 affect?

CVE-2004-1378 affects jabberd, jadc2s. Severity is medium (CVSS 5.0). The expat XML parser code, as used in the open source Jabber (jabberd) 1.4.3 and earlier, jadc2s 0.9.0 and earlier, and possibly other packages, allows remote attackers to cause a denial of service (application crash) via a malformed packet

How urgent is CVE-2004-1378?

Priority 39/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.