cve-2013-0188
Vulnerability from cvelistv5

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2013-0189, CVE-2013-0191. Reason: this identifier was intended for one issue, but it was inadvertently associated with multiple issues. Notes: All CVE users should consult CVE-2013-0189 and CVE-2013-0191 to determine which ID is appropriate. All references and descriptions in this candidate have been removed to prevent accidental usage

Show details on NVD website


{
   containers: {
      cna: {
         providerMetadata: {
            dateUpdated: "2013-10-04T23:00:00Z",
            orgId: "53f830b8-0a3f-465b-8143-3b8a9948e749",
            shortName: "redhat",
         },
         rejectedReasons: [
            {
               lang: "en",
               value: "DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2013-0189, CVE-2013-0191.  Reason: this identifier was intended for one issue, but it was inadvertently associated with multiple issues.  Notes: All CVE users should consult CVE-2013-0189 and CVE-2013-0191 to determine which ID is appropriate.  All references and descriptions in this candidate have been removed to prevent accidental usage",
            },
         ],
      },
   },
   cveMetadata: {
      assignerOrgId: "53f830b8-0a3f-465b-8143-3b8a9948e749",
      assignerShortName: "redhat",
      cveId: "CVE-2013-0188",
      datePublished: "2013-10-04T23:00:00Z",
      dateRejected: "2022-10-03T00:00:00",
      dateReserved: "2012-12-06T00:00:00Z",
      dateUpdated: "2024-09-17T01:47:02.689Z",
      state: "REJECTED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.0",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2013-0188\",\"sourceIdentifier\":\"secalert@redhat.com\",\"published\":\"2013-10-04T23:55:03.407\",\"lastModified\":\"2023-11-07T02:13:46.260\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2013-0189, CVE-2013-0191.  Reason: this identifier was intended for one issue, but it was inadvertently associated with multiple issues.  Notes: All CVE users should consult CVE-2013-0189 and CVE-2013-0191 to determine which ID is appropriate.  All references and descriptions in this candidate have been removed to prevent accidental usage\"}],\"metrics\":{},\"references\":[]}}",
   },
}


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.