FKIE_CVE-2024-42013

Vulnerability from fkie_nvd - Published: 2025-01-22 16:15 - Updated: 2025-02-04 19:15
Severity ?
6.4 (Medium) - CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Summary
In GRAU DATA Blocky before 3.1, Blocky-Gui has a Client-Side Enforcement of Server-Side Security vulnerability. An attacker with Windows administrative or debugging privileges can patch a binary in memory or on disk to bypass the password login requirement and gain full access to all functions of the program.
References
cve@mitre.orghttps://www.blockyforveeam.com/en/security-bulletin-2024-06-25/
cve@mitre.orghttps://www.graudata.com/en/products/protection-against-ransomware/blocky-for-veeam/
Impacted products
Vendor Product Version
To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In GRAU DATA Blocky before 3.1, Blocky-Gui has a Client-Side Enforcement of Server-Side Security vulnerability. An attacker with Windows administrative or debugging privileges can patch a binary in memory or on disk to bypass the password login requirement and gain full access to all functions of the program."
    },
    {
      "lang": "es",
      "value": "En GRAU DATA Blocky anterior a la versi\u00f3n 3.1, Blocky-Gui tiene una vulnerabilidad de aplicaci\u00f3n de la seguridad del lado del servidor en el lado del cliente. Un atacante con privilegios administrativos o de depuraci\u00f3n de Windows puede aplicar un parche a un binario en la memoria o en el disco para eludir el requisito de inicio de sesi\u00f3n con contrase\u00f1a y obtener acceso completo a todas las funciones del programa."
    }
  ],
  "id": "CVE-2024-42013",
  "lastModified": "2025-02-04T19:15:31.570",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 6.4,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 0.5,
        "impactScore": 5.9,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-01-22T16:15:29.303",
  "references": [
    {
      "source": "cve@mitre.org",
      "url": "https://www.blockyforveeam.com/en/security-bulletin-2024-06-25/"
    },
    {
      "source": "cve@mitre.org",
      "url": "https://www.graudata.com/en/products/protection-against-ransomware/blocky-for-veeam/"
    }
  ],
  "sourceIdentifier": "cve@mitre.org",
  "vulnStatus": "Awaiting Analysis",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-863"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.