FKIE_CVE-2013-4615

Vulnerability from fkie_nvd - Published: 2013-06-21 21:55 - Updated: 2026-06-16 23:57
Severity
Summary
The Canon MG3100, MG5300, MG6100, MP495, MX340, MX870, MX890, MX920, and MX922 printers allow remote attackers to cause a denial of service (device hang) via a crafted LAN_TXT24 parameter to English/pages_MacUS/cgi_lan.cgi followed by a direct request to English/pages_MacUS/lan_set_content.html. NOTE: the vendor has apparently responded by stating "Canon believes that its printers will not have to deal with unauthorized access to the network from an external location as long as the printers are used in a secured environment."

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "source": "cve@mitre.org"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:h:canon:mg3100_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "CA808CB1-E232-45A7-8913-03DDD4D967AA",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mg5300_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "4A7BF24E-0FE5-41E6-B4AF-5CEC5ED0AB3E",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mg6100_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "5C007C65-9187-4593-B236-025831220B8C",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mp340_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "F038B929-787C-4350-B1A4-F2E0F12969FE",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mp495_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "6A7687B9-537C-47CB-AA7B-DE57725B6E89",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mx870_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "555BD45B-2B53-42BE-B76B-03205EADD821",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mx890_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "AD762566-16C3-4391-B3C4-A0247AA082AF",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mx920_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "C74EB1F2-29DA-4835-B2D0-AB96CB1B4FB2",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:h:canon:mx922_printer:-:*:*:*:*:*:*:*",
              "matchCriteriaId": "08F6F82C-6EF6-40E6-A6C5-D2B4952B02FC",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The Canon MG3100, MG5300, MG6100, MP495, MX340, MX870, MX890, MX920, and MX922 printers allow remote attackers to cause a denial of service (device hang) via a crafted LAN_TXT24 parameter to English/pages_MacUS/cgi_lan.cgi followed by a direct request to English/pages_MacUS/lan_set_content.html.  NOTE: the vendor has apparently responded by stating \"Canon believes that its printers will not have to deal with unauthorized access to the network from an external location as long as the printers are used in a secured environment.\""
    },
    {
      "lang": "es",
      "value": "Las impresoras Canon MG3100, MG5300, MG6100, MP495, MX340, MX870, MX890, MX920 y MX922  permite a atacantes remotos provocar una denegaci\u00f3n de servicio (cuelgue del dispositivo) a trav\u00e9s de un par\u00e1metro LAN_TXT24 especialmente dise\u00f1ado a English/pages_MacUS/cgi_lan.cgi seguido de una petici\u00f3n directa a   English/pages_MacUS/lan_set_content.html. NOTA: el vendedor ha respondido diciendo \"Canon cree que sus impresoras no tendr\u00e1n que hacer frente a accesos no autorizados a la red desde una ubicaci\u00f3n externa, siempre y cuando las impresoras se utilizan en un entorno seguro.\""
    }
  ],
  "id": "CVE-2013-4615",
  "lastModified": "2026-06-16T23:57:36.153",
  "metrics": {
    "cvssMetricV2": [
      {
        "acInsufInfo": false,
        "baseSeverity": "MEDIUM",
        "cvssData": {
          "accessComplexity": "LOW",
          "accessVector": "NETWORK",
          "authentication": "NONE",
          "availabilityImpact": "PARTIAL",
          "baseScore": 5.0,
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "vectorString": "AV:N/AC:L/Au:N/C:N/I:N/A:P",
          "version": "2.0"
        },
        "exploitabilityScore": 10.0,
        "impactScore": 2.9,
        "obtainAllPrivilege": false,
        "obtainOtherPrivilege": false,
        "obtainUserPrivilege": false,
        "source": "nvd@nist.gov",
        "type": "Primary",
        "userInteractionRequired": false
      }
    ]
  },
  "published": "2013-06-21T21:55:01.057",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "http://archives.neohapsis.com/archives/fulldisclosure/2013-06/0146.html"
    },
    {
      "source": "cve@mitre.org",
      "url": "http://www.mattandreko.com/2013/06/canon-y-u-no-security.html"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/dos/http/canon_wireless_printer.rb"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://archives.neohapsis.com/archives/fulldisclosure/2013-06/0146.html"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "http://www.mattandreko.com/2013/06/canon-y-u-no-security.html"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "url": "https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/dos/http/canon_wireless_printer.rb"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.