jvndb-2004-000169
Vulnerability from jvndb
Published
2008-05-21 00:00
Modified
2008-05-21 00:00
Severity ?
() - -
Summary
LHa Vuffer Overflow Vulnerability in Testing and Extracting Process
Details
LHa for UNIX does not handle the header length information properly when testing or extracting an archive, which could lead to buffer overflow.
Show details on JVN DB website


{
   "@rdf:about": "https://jvndb.jvn.jp/en/contents/2004/JVNDB-2004-000169.html",
   "dc:date": "2008-05-21T00:00+09:00",
   "dcterms:issued": "2008-05-21T00:00+09:00",
   "dcterms:modified": "2008-05-21T00:00+09:00",
   description: "LHa for UNIX does not handle the header length information properly when testing or extracting an archive, which could lead to buffer overflow.",
   link: "https://jvndb.jvn.jp/en/contents/2004/JVNDB-2004-000169.html",
   "sec:cpe": [
      {
         "#text": "cpe:/a:lha_for_unix_project:lha_for_unix",
         "@product": "LHa for UNIX",
         "@vendor": "LHa for UNIX project",
         "@version": "2.2",
      },
      {
         "#text": "cpe:/o:redhat:enterprise_linux",
         "@product": "Red Hat Enterprise Linux",
         "@vendor": "Red Hat, Inc.",
         "@version": "2.2",
      },
      {
         "#text": "cpe:/o:redhat:enterprise_linux_desktop",
         "@product": "Red Hat Enterprise Linux Desktop",
         "@vendor": "Red Hat, Inc.",
         "@version": "2.2",
      },
      {
         "#text": "cpe:/o:redhat:linux",
         "@product": "Red Hat Linux",
         "@vendor": "Red Hat, Inc.",
         "@version": "2.2",
      },
      {
         "#text": "cpe:/o:redhat:linux_advanced_workstation",
         "@product": "Red Hat Linux Advanced Workstation",
         "@vendor": "Red Hat, Inc.",
         "@version": "2.2",
      },
   ],
   "sec:cvss": {
      "@score": "10.0",
      "@severity": "High",
      "@type": "Base",
      "@vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C",
      "@version": "2.0",
   },
   "sec:identifier": "JVNDB-2004-000169",
   "sec:references": [
      {
         "#text": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-0234",
         "@id": "CVE-2004-0234",
         "@source": "CVE",
      },
      {
         "#text": "http://nvd.nist.gov/nvd.cfm?cvename=CVE-2004-0234",
         "@id": "CVE-2004-0234",
         "@source": "NVD",
      },
      {
         "#text": "http://oval.mitre.org/repository/data/getDef?id=oval:org.mitre.oval:def:977",
         "@id": "977",
         "@source": "OVAL",
      },
      {
         "#text": "http://www.securityfocus.com/bid/10243",
         "@id": "10243",
         "@source": "BID",
      },
      {
         "#text": "http://marc.info/?l=bugtraq&m=108422737918885&w=2",
         "@id": "LHA Advisory + Patch",
         "@source": "BID",
      },
      {
         "#text": "http://xforce.iss.net/xforce/xfdb/16012",
         "@id": "16012",
         "@source": "XF",
      },
      {
         "#text": "http://securitytracker.com/id?1015866",
         "@id": "1015866",
         "@source": "SECTRACK",
      },
      {
         "#text": "http://www.frsirt.com/english/advisories/2006/1220",
         "@id": "FrSIRT/ADV-2006-1220",
         "@source": "FRSIRT",
      },
      {
         "#text": "http://osvdb.org/5753",
         "@id": "5753",
         "@source": "OSVDB",
      },
      {
         "#text": "http://osvdb.org/5754",
         "@id": "5754",
         "@source": "OSVDB",
      },
   ],
   title: "LHa Vuffer Overflow Vulnerability in Testing and Extracting Process",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.