[ Date Prev ][Date Next][ Thread Prev ][Thread Next][ Date Index ][ Thread Index ]

Re: Survey: Use of Same Attack/Same Codebase content decision inVDB's

To : "Steven M. Christey" < coley@linus.mitre.org >
Subject : Re: Survey: Use of Same Attack/Same Codebase content decision inVDB's
From : Gene Spafford < spaf@cs.purdue.edu >
Date : Wed, 30 Jun 1999 21:05:24 -0500
Cc : cve-review@linus.mitre.org
In-Reply-To : < 199906302345.TAA03673@basie.mitre.org >
References : < 199906302345.TAA03673@basie.mitre.org >
Reply-To : spaf@cs.purdue.edu

The mechanism I have used in my personal database has been that of
"same attack + same codebase".   If the codebase is different, then
even if the same attack triggers both then it may be that different
attacks could trigger each, so they deserve separate entries.

---spaf

References :
- Survey: Use of Same Attack/Same Codebase content decision in VDB's
  - From: "Steven M. Christey" <coley@linus.mitre.org>

Prev by Date: Survey: Use of Same Attack/Same Codebase content decision in VDB's
Prev by thread: Survey: Use of Same Attack/Same Codebase content decision in VDB's
Index(es):
- Date
- Thread

Page Last Updated or Reviewed: May 22, 2007

Site Map | Terms of Use | Privacy Policy | Contact Us | Follow CVE

Use of the CVE^™ List and the associated references from this website are subject to the terms of use . CVE is sponsored by the U.S. Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA). Copyright © 1999–2021, The MITRE Corporation . CVE is a registered trademark and the CVE logo is a trademark of The MITRE Corporation.