ghsa-v8fp-2p2f-6r3c
Vulnerability from github
Published
2022-05-01 23:44
Modified
2022-05-01 23:44
Details

The Korn shell (aka mksh) before R33d on MirOS (aka MirBSD) does not flush the tty's I/O when invoking mksh in a new terminal, which allows local users to gain privileges by opening a virtual terminal and entering command sequences, which might later be executed in opportunistic circumstances by a different user who launches mksh and specifies that terminal with the -T option.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2008-1845"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2008-04-16T17:05:00Z",
    "severity": "HIGH"
  },
  "details": "The Korn shell (aka mksh) before R33d on MirOS (aka MirBSD) does not flush the tty\u0027s I/O when invoking mksh in a new terminal, which allows local users to gain privileges by opening a virtual terminal and entering command sequences, which might later be executed in opportunistic circumstances by a different user who launches mksh and specifies that terminal with the -T option.",
  "id": "GHSA-v8fp-2p2f-6r3c",
  "modified": "2022-05-01T23:44:09Z",
  "published": "2022-05-01T23:44:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2008-1845"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/41794"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/29803"
    },
    {
      "type": "WEB",
      "url": "http://www.mirbsd.org/mksh.htm#clog"
    },
    {
      "type": "WEB",
      "url": "http://www.osvdb.org/44365"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/28768"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


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