fkie_cve-2010-0228
Vulnerability from fkie_nvd
Published
2010-01-07 19:30
Modified
2025-04-09 00:30
Severity ?
Summary
Verbatim Corporate Secure and Corporate Secure FIPS Edition USB flash drives use a fixed 256-bit key for obtaining access to the cleartext drive contents, which makes it easier for physically proximate attackers to read or modify data by determining and providing this key.
Impacted products
Vendor Product Version
verbatim corporate_secure *
verbatim corporate_secure *



{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:h:verbatim:corporate_secure:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "3BCF538F-945E-484F-847A-77D148E569FD",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:h:verbatim:corporate_secure:*:*:fips:*:*:*:*:*",
                     matchCriteriaId: "1B85262D-B58D-4935-BAE2-A28A79F2C369",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Verbatim Corporate Secure and Corporate Secure FIPS Edition USB flash drives use a fixed 256-bit key for obtaining access to the cleartext drive contents, which makes it easier for physically proximate attackers to read or modify data by determining and providing this key.",
      },
      {
         lang: "es",
         value: "Los dispositivos flash USB Verbatim Corporate Secure y Corporate Secure FIPS Edition utilizan una solución de clave de 256-bit para obtener acceso al contenido del dispositivo en texto plano, lo que hace más fácil a atacantes físicamente próximos leer o modificar información determinando y proporcionando esta clave.",
      },
   ],
   id: "CVE-2010-0228",
   lastModified: "2025-04-09T00:30:58.490",
   metrics: {
      cvssMetricV2: [
         {
            acInsufInfo: false,
            baseSeverity: "MEDIUM",
            cvssData: {
               accessComplexity: "LOW",
               accessVector: "LOCAL",
               authentication: "NONE",
               availabilityImpact: "PARTIAL",
               baseScore: 4.6,
               confidentialityImpact: "PARTIAL",
               integrityImpact: "PARTIAL",
               vectorString: "AV:L/AC:L/Au:N/C:P/I:P/A:P",
               version: "2.0",
            },
            exploitabilityScore: 3.9,
            impactScore: 6.4,
            obtainAllPrivilege: false,
            obtainOtherPrivilege: true,
            obtainUserPrivilege: false,
            source: "nvd@nist.gov",
            type: "Primary",
            userInteractionRequired: false,
         },
      ],
   },
   published: "2010-01-07T19:30:00.713",
   references: [
      {
         source: "cve@mitre.org",
         url: "http://blogs.zdnet.com/hardware/?p=6655",
      },
      {
         source: "cve@mitre.org",
         url: "http://it.slashdot.org/story/10/01/05/1734242/",
      },
      {
         source: "cve@mitre.org",
         url: "http://www.h-online.com/security/news/item/NIST-certified-USB-Flash-drives-with-hardware-encryption-cracked-895308.html",
      },
      {
         source: "cve@mitre.org",
         tags: [
            "Vendor Advisory",
         ],
         url: "http://www.verbatim.com/security/security-update.cfm",
      },
      {
         source: "cve@mitre.org",
         url: "https://www.ironkey.com/usb-flash-drive-flaw-exposed",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://blogs.zdnet.com/hardware/?p=6655",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://it.slashdot.org/story/10/01/05/1734242/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://www.h-online.com/security/news/item/NIST-certified-USB-Flash-drives-with-hardware-encryption-cracked-895308.html",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "http://www.verbatim.com/security/security-update.cfm",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://www.ironkey.com/usb-flash-drive-flaw-exposed",
      },
   ],
   sourceIdentifier: "cve@mitre.org",
   vulnStatus: "Deferred",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-310",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.