GHSA-PC2Q-JCXQ-RJRR

Vulnerability from github – Published: 2023-02-08 18:18 – Updated: 2023-02-08 22:40
VLAI?
Summary
Sensitive Information leak via Script File in TinaCMS
Details

Impact

Sensitive Information leaked via script File in TinaCMS. Sites building with @tinacms/cli >= 1.0.0 && < 1.0.9 that store sensitive values in process.env var are impacted. If you're on a version prior to 1.0.0 this vulnerability does not affect you.

If your Tina-enabled website has sensitive credentials stored as environment variables (eg. Algolia API keys) you should rotate those keys immediately.

Patches

This issue has been patched in @tinacms/cli@1.0.9

Workarounds

Upgrading, and rotating secure & exposed keys is required for the proper fix.

References

https://github.com/tinacms/tinacms/pull/3584

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@tinacms/cli"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.0.0"
            },
            {
              "fixed": "1.0.9"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-25164"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-02-08T18:18:05Z",
    "nvd_published_at": "2023-02-08T20:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nSensitive Information leaked via script File in TinaCMS. Sites building with @tinacms/cli \u003e= 1.0.0 \u0026\u0026 \u003c 1.0.9 that store sensitive values in process.env var are impacted. If you\u0027re on a version prior to 1.0.0 this vulnerability does not affect you.\n\nIf your Tina-enabled website has sensitive credentials stored as environment variables (eg. Algolia API keys) you should rotate those keys immediately.\n\n### Patches\n\nThis issue has been patched in @tinacms/cli@1.0.9\n\n### Workarounds\n\nUpgrading, and rotating secure \u0026 exposed keys is required for the proper fix.\n\n### References\n\nhttps://github.com/tinacms/tinacms/pull/3584",
  "id": "GHSA-pc2q-jcxq-rjrr",
  "modified": "2023-02-08T22:40:18Z",
  "published": "2023-02-08T18:18:05Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/tinacms/tinacms/security/advisories/GHSA-pc2q-jcxq-rjrr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-25164"
    },
    {
      "type": "WEB",
      "url": "https://github.com/tinacms/tinacms/pull/3584"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/tinacms/tinacms"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Sensitive Information leak via Script File in TinaCMS"
}


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…