Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-1310: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-1999-1022. Reason: This candida

0
Medium
VulnerabilityCVE-1999-1310cve-1999-1310
Published: Fri Nov 04 1994 (11/04/1994, 05:00:00 UTC)
Source: NVD

Description

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-1999-1022. Reason: This candidate is a duplicate of CVE-1999-1022. Notes: All CVE users should reference CVE-1999-1022 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

AI-Powered Analysis

AILast updated: 07/02/2025, 02:09:52 UTC

Technical Analysis

The provided information pertains to CVE-1999-1310, which is not an active or valid vulnerability entry. This CVE identifier has been explicitly rejected and marked as a duplicate of CVE-1999-1022. The description states that all references and descriptions associated with CVE-1999-1310 have been removed to prevent accidental usage. Therefore, no technical details, affected versions, or exploit information are available for this candidate. The original vulnerability details should be referenced under CVE-1999-1022 instead. Since CVE-1999-1310 is a rejected candidate number, it does not represent a security threat or vulnerability on its own.

Potential Impact

As CVE-1999-1310 is a rejected and duplicate CVE entry with no associated technical details or exploit information, it poses no direct impact to organizations. European organizations are not affected by this CVE identifier itself. Any potential impact would be related to the original CVE-1999-1022, which should be consulted separately for relevant risk assessment. Without specific details, no meaningful impact analysis can be performed for this rejected candidate.

Mitigation Recommendations

No mitigation actions are applicable for CVE-1999-1310 since it is a rejected and duplicate CVE entry. Organizations should instead focus on any mitigation or patching guidance related to CVE-1999-1022 if that vulnerability is relevant to their environment. It is recommended to maintain up-to-date vulnerability management practices and ensure that CVE references are verified against authoritative sources to avoid confusion caused by duplicate or rejected CVE entries.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32ab6fd31d6ed7de443

Added to database: 5/20/2025, 3:43:38 PM

Last enriched: 7/2/2025, 2:09:52 AM

Last updated: 2/7/2026, 7:28:43 AM

Views: 23

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats