Vulnerability from bitnami_vulndb
Published
2025-01-27 07:15
Modified
2025-03-02 07:44
Summary
Details

Rejected reason: This Record was REJECTED after determining it is not in compliance with CVE Program requirements regarding assignment for vulnerabilities


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "node",
        "purl": "pkg:bitnami/node"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "0.12.18"
            },
            {
              "introduced": "1.0.0"
            },
            {
              "last_affected": "1.8.4"
            },
            {
              "introduced": "2.0.0"
            },
            {
              "last_affected": "2.13.2"
            },
            {
              "introduced": "3.0.0"
            },
            {
              "last_affected": "3.3.1"
            },
            {
              "introduced": "4.0.0"
            },
            {
              "last_affected": "4.9.1"
            },
            {
              "introduced": "5.0.0"
            },
            {
              "last_affected": "5.12.0"
            },
            {
              "introduced": "6.0.0"
            },
            {
              "last_affected": "6.17.1"
            },
            {
              "introduced": "7.0.0"
            },
            {
              "last_affected": "7.10.1"
            },
            {
              "introduced": "8.0.0"
            },
            {
              "last_affected": "8.17.0"
            },
            {
              "introduced": "9.0.0"
            },
            {
              "last_affected": "9.11.2"
            },
            {
              "introduced": "10.0.0"
            },
            {
              "last_affected": "10.24.1"
            },
            {
              "introduced": "11.0.0"
            },
            {
              "last_affected": "11.15.0"
            },
            {
              "introduced": "12.0.0"
            },
            {
              "last_affected": "12.22.12"
            },
            {
              "introduced": "13.0.0"
            },
            {
              "last_affected": "13.14.0"
            },
            {
              "introduced": "14.0.0"
            },
            {
              "last_affected": "14.21.3"
            },
            {
              "introduced": "15.0.0"
            },
            {
              "last_affected": "15.14.0"
            },
            {
              "introduced": "16.0.0"
            },
            {
              "last_affected": "16.20.2"
            },
            {
              "introduced": "17.0.0"
            },
            {
              "last_affected": "17.9.1"
            }
          ],
          "type": "SEMVER"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-23087"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:nodejs:node.js:*:*:*:*:*:*:*:*"
    ],
    "severity": "Unknown"
  },
  "details": "Rejected reason: This Record was REJECTED after determining it is not in compliance with CVE Program requirements regarding assignment for vulnerabilities",
  "id": "BIT-node-2025-23087",
  "modified": "2025-03-02T07:44:48.340Z",
  "published": "2025-01-27T07:15:36.528Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://nodejs.org/en/blog/vulnerability/january-2025-security-releases"
    },
    {
      "type": "WEB",
      "url": "https://endoflife.date/nodejs"
    }
  ],
  "schema_version": "1.5.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…