CVE-2002-1719: Unknown vulnerability in Bavo 0.3 allows remote attackers to modify posted messages.

Routine

MEDIUM 5.0DOWNGRADE

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

Unknown vulnerability in Bavo 0.3 allows remote attackers to modify posted messages.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	2.1% (top 19%)
CISA exploited list	No
Published	2002-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: bavo

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

Am I affected?

Timeline

2002-12-31 05:00 UTCPublished CVE record published
2026-06-16 21:59 UTCUpdated Record last modified

bavo bavo DOWNGRADE

Affected: 0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.3

1. Check installed version

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

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

apt-cache madison bavo sudo apt install bavo=<VERSION_BEFORE_0.3> sudo apt-mark hold bavo

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

dnf --showduplicates list bavo sudo dnf downgrade bavo-<VERSION_BEFORE_0.3> sudo dnf versionlock add bavo

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

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

Is CVE-2002-1719 being exploited?

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

CVE-2002-1719 affects bavo. Severity is medium (CVSS 5.0). Unknown vulnerability in Bavo 0.3 allows remote attackers to modify posted messages.

How urgent is CVE-2002-1719?

Priority 38/100. No elevated risk signals yet.

References

← Back to latest CVEs