rustsec-2019-0024
Vulnerability from osv_rustsec
Published
2019-10-08 12:00
Modified
2022-11-05 17:45
Summary
Test advisory with associated example crate
Details

This is a test advisory useful for verifying RustSec tooling and vulnerability detection pipelines are working correctly. Aside from the fact that it is filed against an example crate, it is otherwise considered by the Advisory Database itself to be a normal security advisory.

It's filed against rustsec-example-crate, an otherwise completely empty crate with no functionality or code, which has three releases:

  • v0.0.0 - unaffected by this advisory (but yanked from crates.io)
  • v0.0.1 - vulnerable according to this advisory
  • v1.0.0 - patched by this advisory
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "categories": [],
        "cvss": null,
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "rustsec-example-crate",
        "purl": "pkg:cargo/rustsec-example-crate"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.1"
            },
            {
              "fixed": "1.0.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "This is a test advisory useful for verifying RustSec tooling and vulnerability\ndetection pipelines are working correctly. Aside from the fact that it is filed\nagainst an example crate, it is otherwise considered by the Advisory Database\nitself to be a normal security advisory.\n\nIt\u0027s filed against `rustsec-example-crate`, an otherwise completely empty crate\nwith no functionality or code, which has three releases:\n\n- [v0.0.0] - *unaffected* by this advisory (but *yanked* from crates.io)\n- [v0.0.1] - *vulnerable* according to this advisory\n- [v1.0.0] - *patched* by this advisory\n\n[v0.0.0]: https://crates.io/crates/rustsec-example-crate/0.0.0\n[v0.0.1]: https://crates.io/crates/rustsec-example-crate/0.0.1\n[v1.0.0]: https://crates.io/crates/rustsec-example-crate/1.0.0",
  "id": "RUSTSEC-2019-0024",
  "modified": "2022-11-05T17:45:24Z",
  "published": "2019-10-08T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/rustsec-example-crate"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2019-0024.html"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/RustSec/advisory-db/issues/158"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "Test advisory with associated example crate"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.