jvndb-2024-006787
Vulnerability from jvndb
Published
2024-08-29 14:07
Modified
2024-08-29 14:07
Severity ?
Summary
xfpt vulnerable to stack-based buffer overflow
Details
xfpt fails to handle appropriately some parameters inside the input data, resulting in a stack-based buffer overflow vulnerability (CWE-121). Yuhei Kawakoya of NTT Security Holdings Corporation reported this vulnerability to JPCERT/CC. JPCERT/CC coordinated with the developer.
Impacted products
Philip Hazelxfpt
Show details on JVN DB website


{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-006787.html",
  "dc:date": "2024-08-29T14:07+09:00",
  "dcterms:issued": "2024-08-29T14:07+09:00",
  "dcterms:modified": "2024-08-29T14:07+09:00",
  "description": "xfpt fails to handle appropriately some parameters inside the input data, resulting in a stack-based buffer overflow vulnerability (CWE-121).\r\n\r\nYuhei Kawakoya of NTT Security Holdings Corporation reported this vulnerability to JPCERT/CC.\r\nJPCERT/CC coordinated with the developer.",
  "link": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-006787.html",
  "sec:cpe": {
    "#text": "cpe:/a:misc:philip_hazel_xfpt",
    "@product": "xfpt",
    "@vendor": "Philip Hazel",
    "@version": "2.2"
  },
  "sec:cvss": {
    "@score": "7.0",
    "@severity": "High",
    "@type": "Base",
    "@vector": "CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
    "@version": "3.0"
  },
  "sec:identifier": "JVNDB-2024-006787",
  "sec:references": [
    {
      "#text": "https://jvn.jp/en/vu/JVNVU96498690/index.html",
      "@id": "JVNVU#96498690",
      "@source": "JVN"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-43700",
      "@id": "CVE-2024-43700",
      "@source": "CVE"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/121.html",
      "@id": "CWE-121",
      "@title": "Stack-based Buffer Overflow(CWE-121)"
    }
  ],
  "title": "xfpt vulnerable to stack-based buffer overflow"
}


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.