CVE-2005-2790: BFCommand & Control Server Manager BFCC 1.22_A and earlier, and BFVCC 2.14_B and earlier, relies on the client

This month

HIGH 7.5UPGRADEDOWNGRADE

CVE-2005-2790 is a high-severity flaw (CVSS 7.5) affecting bfcc, bfvcc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BFCommand & Control Server Manager BFCC 1.22_A and earlier, and BFVCC 2.14_B and earlier, relies on the client to enforce permissions and perform actions such as disconnections, which allows remote attackers to bypass administrative restrictions via a modified client.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.7% (top 22%)
CISA exploited list	No
Published	2005-09-02
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: bfcommand and control software

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

Am I affected?

Timeline

2005-09-02 23:03 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

bfcommand and control software bfcc UPGRADE

Affected: <= 1.22_a

Fixed in: newer than 1.22_a

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 1.22_a (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bfcc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bfcc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

bfcommand and control software bfvcc DOWNGRADE

Affected: 2.00_a · 2.14_b

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.00_a

1. Check installed version

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

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

apt-cache madison bfvcc sudo apt install bfvcc=<VERSION_BEFORE_2.00_a> sudo apt-mark hold bfvcc

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

dnf --showduplicates list bfvcc sudo dnf downgrade bfvcc-<VERSION_BEFORE_2.00_a> sudo dnf versionlock add bfvcc

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-2005-2790?

bfcc: upgrade to newer than 1.22_a; bfvcc: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2790 being exploited?

CVE-2005-2790 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-2005-2790 affect?

CVE-2005-2790 affects bfcc, bfvcc. Severity is high (CVSS 7.5). BFCommand & Control Server Manager BFCC 1.22_A and earlier, and BFVCC 2.14_B and earlier, relies on the client to enforce permissions and perform actions such as disconnections, which allows remote attackers to bypass administrative restric

How urgent is CVE-2005-2790?

Priority 51/100. High severity; Public exploit reference

Related CVEs

CVE-2005-2791 MEDIUM 5.0 UPGRADE DOWNGRADE BFCommand & Control Server Manager BFCC 1.22_A and earlier, and BFVCC 2.14_B and earlier, allows remote attack
CVE-2005-2789 HIGH 7.5 UPGRADE DOWNGRADE BFCommand & Control Server Manager BFCC 1.22_A and earlier, and BFVCC 2.14_B and earlier, allows remote attack

References

← Back to latest CVEs