Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2002-2414: Opera 6.0.3, when using Squid 2.4 for HTTPS proxying, does not properly handle when accepting a non-global cer

32
Routine
MEDIUM 4.3DOWNGRADEDOWNGRADE

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

Opera 6.0.3, when using Squid 2.4 for HTTPS proxying, does not properly handle when accepting a non-global certificate authority (CA) certificate from a site and establishing a subsequent HTTPS connection, which allows remote attackers to cause a denial of service (crash).

Why this priority

  • No elevated risk signals yet

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

Risk facts

CVSS score4.3 (Medium)
EPSS exploit chance1.2% (top 32%)
CISA exploited listNo
Published2002-12-31
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: opera software · squid

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

opera software opera DOWNGRADE
Affected: 6.0.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0.3
1. Check installed version
apt-cache policy opera || rpm -q opera || opera --version
2. No fixed release: DOWNGRADE to a release before 6.0.3 (Debian / Ubuntu)
apt-cache madison opera sudo apt install opera=<VERSION_BEFORE_6.0.3> sudo apt-mark hold opera
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list opera sudo dnf downgrade opera-<VERSION_BEFORE_6.0.3> sudo dnf versionlock add opera
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.
squid squid DOWNGRADE
Affected: 2.4
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.4
1. Check installed version
apt-cache policy squid || rpm -q squid || squid --version
2. No fixed release: DOWNGRADE to a release before 2.4 (Debian / Ubuntu)
apt-cache madison squid sudo apt install squid=<VERSION_BEFORE_2.4> sudo apt-mark hold squid
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list squid sudo dnf downgrade squid-<VERSION_BEFORE_2.4> sudo dnf versionlock add squid
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-2414?

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

Is CVE-2002-2414 being exploited?

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

CVE-2002-2414 affects opera, squid. Severity is medium (CVSS 4.3). Opera 6.0.3, when using Squid 2.4 for HTTPS proxying, does not properly handle when accepting a non-global certificate authority (CA) certificate from a site and establishing a subsequent HTTPS connection, which allows remote attackers to c

How urgent is CVE-2002-2414?

Priority 32/100. No elevated risk signals yet.

Software pages

Squid vulnerabilities

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.