Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2005-1961: Unknown vulnerability in ObjectWeb Consortium C-JDBC before 1.3.1 allows local users to bypass intended access

22
Routine
MEDIUM 4.6DOWNGRADE

CVE-2005-1961 is a medium-severity flaw (CVSS 4.6) affecting consortium c-jdbc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Unknown vulnerability in ObjectWeb Consortium C-JDBC before 1.3.1 allows local users to bypass intended access restrictions and obtain the cache results from another user.

Why this priority

  • No elevated risk signals yet

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

Risk facts

CVSS score4.6 (Medium)
EPSS exploit chance0.3% (top 76%)
CISA exploited listNo
Published2005-06-07
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: objectweb

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

objectweb consortium c-jdbc DOWNGRADE
Affected: 1.0 · 1.0.1 · 1.0.2 · 1.0.3 · 1.0.4 · 1.1 · 1.2 · 1.2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.0
1. Check installed version
apt-cache policy consortium-c-jdbc || rpm -q consortium-c-jdbc || consortium-c-jdbc --version
2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)
apt-cache madison consortium-c-jdbc sudo apt install consortium-c-jdbc=<VERSION_BEFORE_1.0> sudo apt-mark hold consortium-c-jdbc
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list consortium-c-jdbc sudo dnf downgrade consortium-c-jdbc-<VERSION_BEFORE_1.0> sudo dnf versionlock add consortium-c-jdbc
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-1961?

consortium c-jdbc: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1961 being exploited?

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

CVE-2005-1961 affects consortium c-jdbc. Severity is medium (CVSS 4.6). Unknown vulnerability in ObjectWeb Consortium C-JDBC before 1.3.1 allows local users to bypass intended access restrictions and obtain the cache results from another user.

How urgent is CVE-2005-1961?

Priority 22/100. No elevated risk signals yet.

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.