Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2004-2107: Finjan SurfinGate 6.0 and 7.0, when running in proxy mode, does not authenticate FHTTP commands on TCP port 31

55
This month
HIGH 7.5DOWNGRADE

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

Finjan SurfinGate 6.0 and 7.0, when running in proxy mode, does not authenticate FHTTP commands on TCP port 3141, which allows remote attackers to use the finjan-parameter-type header to (1) restart the service, (2) use the getlastmsg command to view log information, or (3) use the online command to force a policy update from the database server.

Why this priority

  • High severity
  • EPSS top 5%: very likely to be exploited
  • Public exploit reference

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

Risk facts

CVSS score7.5 (High)
EPSS exploit chance7.7% (top 5%)
CISA exploited listNo
Published2004-12-31
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: finjan software

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

finjan software surfingate DOWNGRADE
Affected: 6.0 · 6.0_1 · 6.0_5 · 7.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
1. Check installed version
apt-cache policy surfingate || rpm -q surfingate || surfingate --version
2. No fixed release: DOWNGRADE to a release before 6.0 (Debian / Ubuntu)
apt-cache madison surfingate sudo apt install surfingate=<VERSION_BEFORE_6.0> sudo apt-mark hold surfingate
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list surfingate sudo dnf downgrade surfingate-<VERSION_BEFORE_6.0> sudo dnf versionlock add surfingate
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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-2107?

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

Is CVE-2004-2107 being exploited?

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

CVE-2004-2107 affects surfingate. Severity is high (CVSS 7.5). Finjan SurfinGate 6.0 and 7.0, when running in proxy mode, does not authenticate FHTTP commands on TCP port 3141, which allows remote attackers to use the finjan-parameter-type header to (1) restart the service, (2) use the getlastmsg comma

How urgent is CVE-2004-2107?

Priority 55/100. High severity; EPSS top 5%: very likely to be exploited; Public exploit reference

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.