fkie_cve-2025-26856
Vulnerability from fkie_nvd
Published
2025-02-20 06:15
Modified
2025-02-20 06:15
Severity ?
7.2 (High) - CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Summary
Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in UD-LT2 firmware Ver.1.00.008_SE and earlier. If an attacker logs in to the affected product with an administrative account and manipulates requests for a certain screen operation, an arbitrary OS command may be executed. This vulnerability was reported on a different screen operation from CVE-2025-20617.
References
vultures@jpcert.or.jphttps://jvn.jp/en/jp/JVN15293958/
vultures@jpcert.or.jphttps://www.iodata.jp/support/information/2025/01_ud-lt2/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "Improper neutralization of special elements used in an OS command ('OS Command Injection') issue exists in UD-LT2 firmware Ver.1.00.008_SE and earlier. If an attacker logs in to the affected product with an administrative account and manipulates requests for a certain screen operation, an arbitrary OS command may be executed. This vulnerability was reported on a different screen operation from CVE-2025-20617.",
      },
      {
         lang: "es",
         value: "La neutralización inadecuada de los elementos especiales utilizados en un problema de comando OS ('inyección de comando de os') existe en el firmware UD-LT2 ver.1.00.008_SE y anterior. Si un atacante inicia sesión en el producto afectado con una cuenta administrativa y manipula las solicitudes de una determinada operación de pantalla, se puede ejecutar un comando Arbitrary OS. Esta vulnerabilidad se informó en una operación de pantalla diferente de CVE-2025-20617.",
      },
   ],
   id: "CVE-2025-26856",
   lastModified: "2025-02-20T06:15:21.673",
   metrics: {
      cvssMetricV30: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 7.2,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "HIGH",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
               version: "3.0",
            },
            exploitabilityScore: 1.2,
            impactScore: 5.9,
            source: "vultures@jpcert.or.jp",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-20T06:15:21.673",
   references: [
      {
         source: "vultures@jpcert.or.jp",
         url: "https://jvn.jp/en/jp/JVN15293958/",
      },
      {
         source: "vultures@jpcert.or.jp",
         url: "https://www.iodata.jp/support/information/2025/01_ud-lt2/",
      },
   ],
   sourceIdentifier: "vultures@jpcert.or.jp",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-78",
            },
         ],
         source: "vultures@jpcert.or.jp",
         type: "Primary",
      },
   ],
}


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.




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.