ghsa-h2wm-p2vg-6pw4
Vulnerability from github
Published
2023-06-09 22:40
Modified
2025-01-09 15:37
Summary
Kredis JSON Possible Deserialization of Untrusted Data Vulnerability
Details

There is a deserialization of untrusted data vulnerability in the Kredis JSON deserialization code. This vulnerability has been assigned the CVE identifier CVE-2023-27531.

'Not affected: None.' 'Versions Affected: All.' 'Fixed Versions: 1.3.0.1'

Impact Carefully crafted JSON data processed by Kredis may result in deserialization of untrusted data, potentially leading to deserialization of unexpected objects in the system.

Any applications using Kredis with JSON are affected.

Releases The fixed releases are available at the normal locations.

Workarounds There are no feasible workarounds for this issue.

Patches To aid users who aren’t able to upgrade immediately we have provided patches for the two supported release series. They are in git-am format and consist of a single changeset.

  • 1-3-0-1-kredis.patch - Patch for 1.3.0 series

Credits Thank you ooooooo_k 7 for reporting this!

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "RubyGems",
        "name": "kredis"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.3.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-27531"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-502"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-06-09T22:40:54Z",
    "nvd_published_at": "2025-01-09T01:15:07Z",
    "severity": "MODERATE"
  },
  "details": "There is a deserialization of untrusted data vulnerability in\nthe Kredis JSON deserialization code. This vulnerability has\nbeen assigned the CVE identifier CVE-2023-27531.\n\n\u0027Not affected: None.\u0027\n\u0027Versions Affected: All.\u0027\n\u0027Fixed Versions: 1.3.0.1\u0027\n\nImpact\n  Carefully crafted JSON data processed by Kredis may result in\n  deserialization of untrusted data, potentially leading to\n  deserialization of unexpected objects in the system.\n\n  Any applications using Kredis with JSON are affected.\n\nReleases\n  The fixed releases are available at the normal locations.\n\nWorkarounds\n  There are no feasible workarounds for this issue.\n\nPatches\n  To aid users who aren\u2019t able to upgrade immediately we have\n  provided patches for the two supported release series. They\n  are in git-am format and consist of a single changeset.\n\n  * 1-3-0-1-kredis.patch - Patch for 1.3.0 series\n\nCredits\n  Thank you ooooooo_k 7 for reporting this!\n",
  "id": "GHSA-h2wm-p2vg-6pw4",
  "modified": "2025-01-09T15:37:28Z",
  "published": "2023-06-09T22:40:54Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-27531"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rails/kredis/commit/d576b7ae5c8d3d74eeb4bd84cad0aa64ffc299fa"
    },
    {
      "type": "WEB",
      "url": "https://discuss.rubyonrails.org/t/cve-2023-27531-possible-deserialization-of-untrusted-data-vulnerability-in-kredis-json/82467"
    },
    {
      "type": "WEB",
      "url": "https://discuss.rubyonrails.org/t/cve-2023-27531-possible-deserialization-of-untrusted-data-vulnerability-in-kredis-json/82467#post_1"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rails/kredis"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rails/kredis/releases/tag/v1.3.0.1"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/kredis/CVE-2023-27531.yml"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Kredis JSON Possible Deserialization of Untrusted Data Vulnerability"
}


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 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.