JVNDB-2024-011256

Vulnerability from jvndb - Published: 2024-10-28 08:33 - Updated:2024-10-28 08:33
Severity
9.1 (Critical) - cvssV3_0 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Summary
Multiple vulnerabilities in Sharp and Toshiba Tec MFPs
Details
MFPs (multifunction printers) provided by Sharp and Toshiba Tec Corporation contain multiple vulnerabilites listed below.
  • Out-of-bounds Read (CWE-125)
    • CVE-2024-42420
    • Out-of-bounds read vulnerabilities coming from improper processing of keyword search input and improper processing of SOAP messages
  • Out-of-bounds Read (CWE-125)
    • CVE-2024-43424
    • Out-of-bounds read vulnerability coming from improper processing of HTTP request headers
  • Out-of-bounds Read (CWE-125)
    • CVE-2024-45829
    • Out-of-bounds read vulnerability in the web page providing data downloading, where query parameters in HTTP requests are improperly processed
  • Path traversal (CWE-22)
    • CVE-2024-45842
    • Improper processing of URI data in HTTP PUT requests leads to path traversal vulnerability, unintended internal files may be retrieved
  • Improper access restriction on some configuration related APIs (CWE-749)
    • CVE-2024-47005
    • Some configuration related APIs are expected to be called by administrative users only, but insufficiently restricted
  • Authentication Bypass Using an Alternate Path (CWE-288)
    • CVE-2024-47406
    • Improper processing of HTTP authentication requests may lead to authentication bypass
  • Improper processing of query parameters in HTTP requests (CWE-644)
    • CVE-2024-47549
    • Improper processing of query parameters of HTTP requests may allow contamination of unintended data to HTTP response headers
  • Reflected Cross-site Scripting (CWE-79)
    • CVE-2024-47801
    • Reflected cross-site scripting vulnerability coming from improper processing of query parameters in HTTP requests
  • Stored Cross-site Scripting (CWE-79)
    • CVE-2024-48870
    • Stored cross-site scripting vulnerability coming from improper input data validation in URI data registration
Sharp Corporation reported these vulnerabilities to JPCERT/CC to notify users of its solution through JVN.
References
Impacted products
Show details on JVN DB website
To clipboard 

{
  "@rdf:about": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-011256.html",
  "dc:date": "2024-10-28T17:33+09:00",
  "dcterms:issued": "2024-10-28T17:33+09:00",
  "dcterms:modified": "2024-10-28T17:33+09:00",
  "description": "MFPs (multifunction printers) provided by Sharp and Toshiba Tec Corporation contain multiple vulnerabilites listed below.\r\n\r\n\u003cul\u003e\r\n\t\u003cli\u003eOut-of-bounds Read (CWE-125)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-42420\u003c/li\u003e\r\n\t\t\u003cli\u003eOut-of-bounds read vulnerabilities coming from improper processing of keyword search input and improper processing of\u0026nbsp;SOAP messages\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eOut-of-bounds Read (CWE-125)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-43424\u003c/li\u003e\r\n\t\t\u003cli\u003eOut-of-bounds read vulnerability coming from improper processing of HTTP request headers\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eOut-of-bounds Read\u0026nbsp;(CWE-125)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-45829\u003c/li\u003e\r\n\t\t\u003cli\u003eOut-of-bounds read vulnerability in the web page providing data downloading, where query parameters in HTTP requests are improperly processed\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003ePath traversal\u0026nbsp;(CWE-22)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-45842\u003c/li\u003e\r\n\t\t\u003cli\u003eImproper processing of URI data in HTTP PUT requests leads to path traversal vulnerability, unintended internal files may be retrieved\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eImproper access restriction on some configuration related\u0026nbsp;APIs (CWE-749)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-47005\u003c/li\u003e\r\n\t\t\u003cli\u003eSome configuration related APIs are expected to be called by administrative users only, but insufficiently restricted\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eAuthentication Bypass Using an Alternate Path\u0026nbsp;(CWE-288)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-47406\u003c/li\u003e\r\n\t\t\u003cli\u003eImproper processing of HTTP authentication requests may lead to authentication bypass\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eImproper processing of query parameters in HTTP requests (CWE-644)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-47549\u003c/li\u003e\r\n\t\t\u003cli\u003eImproper processing of query parameters of HTTP requests may allow contamination of unintended data to HTTP response headers\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eReflected Cross-site Scripting (CWE-79)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-47801\u003c/li\u003e\r\n\t\t\u003cli\u003eReflected cross-site scripting vulnerability coming from improper processing of query parameters in HTTP requests\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\t\u003cli\u003eStored Cross-site Scripting (CWE-79)\r\n\t\u003cul\u003e\r\n\t\t\u003cli\u003eCVE-2024-48870\u003c/li\u003e\r\n\t\t\u003cli\u003eStored cross-site scripting vulnerability coming from improper input data validation in URI data registration\u003c/li\u003e\r\n\t\u003c/ul\u003e\r\n\t\u003c/li\u003e\r\n\u003c/ul\u003e\r\n\r\nSharp Corporation reported these vulnerabilities to JPCERT/CC to notify users of its solution through JVN.",
  "link": "https://jvndb.jvn.jp/en/contents/2024/JVNDB-2024-011256.html",
  "sec:cpe": [
    {
      "#text": "cpe:/a:sharp:multiple_product",
      "@product": "(Multiple Products)",
      "@vendor": "Sharp Corporation",
      "@version": "2.2"
    },
    {
      "#text": "cpe:/a:toshibatec:multiple_product",
      "@product": "(Multiple Products)",
      "@vendor": "TOSHIBA TEC",
      "@version": "2.2"
    }
  ],
  "sec:cvss": {
    "@score": "9.1",
    "@severity": "Critical",
    "@type": "Base",
    "@vector": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
    "@version": "3.0"
  },
  "sec:identifier": "JVNDB-2024-011256",
  "sec:references": [
    {
      "#text": "https://jvn.jp/en/vu/JVNVU95063136/index.html",
      "@id": "JVNVU#95063136",
      "@source": "JVN"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-42420",
      "@id": "CVE-2024-42420",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-43424",
      "@id": "CVE-2024-43424",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-45829",
      "@id": "CVE-2024-45829",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-45842",
      "@id": "CVE-2024-45842",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-47005",
      "@id": "CVE-2024-47005",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-47406",
      "@id": "CVE-2024-47406",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-47549",
      "@id": "CVE-2024-47549",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-47801",
      "@id": "CVE-2024-47801",
      "@source": "CVE"
    },
    {
      "#text": "https://www.cve.org/CVERecord?id=CVE-2024-48870",
      "@id": "CVE-2024-48870",
      "@source": "CVE"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/125.html",
      "@id": "CWE-125",
      "@title": "Out-of-bounds Read(CWE-125)"
    },
    {
      "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
      "@id": "CWE-22",
      "@title": "Path Traversal(CWE-22)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/288.html",
      "@id": "CWE-288",
      "@title": "Authentication Bypass Using an Alternate Path or Channel(CWE-288)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/644.html",
      "@id": "CWE-644",
      "@title": "Improper Neutralization of HTTP Headers for Scripting Syntax(CWE-644)"
    },
    {
      "#text": "https://cwe.mitre.org/data/definitions/749.html",
      "@id": "CWE-749",
      "@title": "Exposed Dangerous Method or Function(CWE-749)"
    },
    {
      "#text": "https://www.ipa.go.jp/en/security/vulnerabilities/cwe.html",
      "@id": "CWE-79",
      "@title": "Cross-site Scripting(CWE-79)"
    }
  ],
  "title": "Multiple vulnerabilities in Sharp and Toshiba Tec MFPs"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.