Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Spoofing attack due to unvalidated KDC in node-krb5

CVE-2016-1000238GHSA-4v9q-hm2p-68c4

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm node-krb5

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Affected versions of node-krb5 do not validate the KDC prior to authenticating, which might allow an attacker with network access and enough time to spoof the KDC and impersonate a valid user without knowing their credentials. Recommendation It appears that this will remain unfixed indefinitely, as the Github issue for this vulnerability has been open since 2015, with no work on it since then. At this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are multiple modules fitting this criteria available on npm..

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-4v9q-hm2p-68c4

  2. Revision 1 · created ·

    Published from osv record GHSA-4v9q-hm2p-68c4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2016-1000238

Advisory: Spoofing attack due to unvalidated KDC in node-krb5
IDs: CVE-2016-1000238, GHSA-4v9q-hm2p-68c4
Record: https://patchnext.com/advisories/cve-2016-1000238 (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-krb5: affected every version

## Suggested inspection (read-only)
- `npm ls node-krb5 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-krb5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-4v9q-hm2p-68c4 (OSV record GHSA-4v9q-hm2p-68c4 lists affected ranges: npm node-krb5 >=0.0.0)
- Verified: https://github.com/advisories/GHSA-4v9q-hm2p-68c4 (GitHub-reviewed advisory GHSA-4v9q-hm2p-68c4 lists affected ranges: npm node-krb5 >=0.0.0)

Commands are suggestions: review each one before running it.

Loading voting…