dbcve.org
Debian LinuxOperating system · Debian

CVE-2007-2442

HIGH · 10.0 CVSS v2.0 Published 2007-06-26
Fix available
A fix is available. Upgrade to after 1.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The gssrpc__svcauth_gssapi function in the RPC library in MIT Kerberos 5 (krb5) 1.6.1 and earlier might allow remote attackers to execute arbitrary code via a zero-length RPC credential, which causes kadmind to free an uninitialized pointer during cleanup.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 3.1= 4.0
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04
Kerberos 5Application
Affected:<= 1.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.6.1
Vendor patch web.mit.edu →
Recommended fix High confidence

Kerberos 5 version 1.6.2 or later (or the latest stable 1.x release available from your distribution)

  1. 1. Identify the currently installed Kerberos 5 version by running: kinit -V or checking the installed package version (e.g., dpkg -l | grep krb5, rpm -q krb5-server)
  2. 2. For Debian Linux 3.1 and 4.0: Update the system package repositories and upgrade the krb5 packages using: apt-get update && apt-get install krb5-kdc krb5-admin-server
  3. 3. For Ubuntu Linux 6.06, 6.10, and 7.04: Update the system package repositories and upgrade the krb5 packages using: sudo apt-get update && sudo apt-get install krb5-kdc krb5-admin-server
  4. 4. If using MIT Kerberos 5 directly from source (not OS packages), download and install Kerberos 5 version 1.6.2 or later from http://web.mit.edu/kerberos/dist/
  5. 5. After upgrading, restart the kadmind service: /etc/init.d/kadmind restart (or service kadmin restart)
  6. 6. Verify the new version is installed: kinit -V
Caveat Major upgrades between Kerberos 5 releases may require configuration adjustments; review the release notes for any database migration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2442 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2442 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data