fkie_cve-2024-1531
Vulnerability from fkie_nvd
Published
2024-03-27 02:15
Modified
2024-11-21 08:50
Severity ?
8.2 (High) - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H
Summary
A vulnerability exists in the stb-language file handling that affects the RTU500 series product versions listed below. A malicious actor could print random memory content in the RTU500 system log, if an authorized user uploads a specially crafted stb-language file.
References
cybersecurity@hitachienergy.comhttps://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true
af854a3a-2127-422b-91ae-364da2661108https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "A vulnerability exists in the stb-language file handling that affects the RTU500 series product versions listed below. A malicious actor could print random memory content in the RTU500 system log, if an authorized user uploads a specially crafted stb-language file.",
      },
      {
         lang: "es",
         value: "Existe una vulnerabilidad en el manejo de archivos en lenguaje stb que afecta a las versiones de productos de la serie RTU500 que se enumeran a continuación. Un actor malintencionado podría imprimir contenido de memoria aleatorio en el registro del sistema RTU500, si un usuario autorizado carga un archivo en lenguaje stb especialmente manipulado.",
      },
   ],
   id: "CVE-2024-1531",
   lastModified: "2024-11-21T08:50:46.133",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 8.2,
               baseSeverity: "HIGH",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "HIGH",
               scope: "CHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.3,
            impactScore: 5.3,
            source: "cybersecurity@hitachienergy.com",
            type: "Secondary",
         },
      ],
   },
   published: "2024-03-27T02:15:11.177",
   references: [
      {
         source: "cybersecurity@hitachienergy.com",
         url: "https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://publisher.hitachienergy.com/preview?DocumentId=8DBD000190&languageCode=en&Preview=true",
      },
   ],
   sourceIdentifier: "cybersecurity@hitachienergy.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-434",
            },
         ],
         source: "cybersecurity@hitachienergy.com",
         type: "Secondary",
      },
   ],
}


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.