GHSA-9H6H-9G78-86F7

Vulnerability from github – Published: 2022-12-29 01:50 – Updated: 2022-12-29 01:50
VLAI
Summary
Yapscan's report receiver server vulnerable to path traversal and log injection
Details

Impact

If you make use of the report receiver server (experimental), a client may be able to forge requests such that arbitrary files on the host can be overwritten (subject to permissions of the yapscan server), leading to loss of data. This is particularly problematic if you do not authenticate clients and/or run the server with elevated permissions.

Patches

Vulnerable versions:

  • v0.18.0
  • v0.19.0 (unreleased)

This problem is patched in version v0.19.1

Workarounds

Update to the newer version is highly encouraged!

Measures to reduce the risk of this include authenticating clients (see --client-ca flag) and containerization of the yapscan server.

References

The tracking issue is #35. There you can find the commits, fixing the issue.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/fkie-cad/yapscan"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.18.0"
            },
            {
              "fixed": "0.19.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-117",
      "CWE-22",
      "CWE-73"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2022-12-29T01:50:20Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\nIf you make use of the **report receiver server** (experimental), a client may be able to forge requests such that arbitrary files on the host can be overwritten (subject to permissions of the yapscan server), leading to loss of data. This is particularly problematic if you do not authenticate clients and/or run the server with elevated permissions.\n\n### Patches\n\nVulnerable versions:\n\n- v0.18.0\n- v0.19.0 (unreleased)\n\nThis problem is patched in version v0.19.1\n\n### Workarounds\n\nUpdate to the newer version is highly encouraged!\n\nMeasures to reduce the risk of this include authenticating clients (see `--client-ca` flag) and containerization of the yapscan server.\n\n### References\n\nThe tracking issue is #35. There you can find the commits, fixing the issue.\n",
  "id": "GHSA-9h6h-9g78-86f7",
  "modified": "2022-12-29T01:50:20Z",
  "published": "2022-12-29T01:50:20Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/fkie-cad/yapscan/security/advisories/GHSA-9h6h-9g78-86f7"
    },
    {
      "type": "WEB",
      "url": "https://github.com/fkie-cad/yapscan/issues/35"
    },
    {
      "type": "WEB",
      "url": "https://github.com/fkie-cad/yapscan/commit/a75a20b50be673b96b1d42187b97f8cfe60728df"
    },
    {
      "type": "WEB",
      "url": "https://github.com/fkie-cad/yapscan/commit/fef9a33ceb66f6b929839f7eaf393b629681bc5d"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/fkie-cad/yapscan"
    },
    {
      "type": "WEB",
      "url": "https://github.com/fkie-cad/yapscan/releases/tag/v0.19.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Yapscan\u0027s report receiver server vulnerable to path traversal and log injection"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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…