fkie_cve-2025-48952
Vulnerability from fkie_nvd
Published
2025-07-04 23:15
Modified
2025-08-06 17:48
Severity ?
Summary
NetAlertX is a network, presence scanner, and alert framework. Prior to version 25.6.7, a vulnerability in the authentication logic allows users to bypass password verification using SHA-256 magic hashes, due to loose comparison in PHP. In vulnerable versions of the application, a password comparison is performed using the `==` operator at line 40 in front/index.php. This introduces a security issue where specially crafted "magic hash" values that evaluate to true in a loose comparison can bypass authentication. Because of the use of `==` instead of the strict `===`, different strings that begin with 0e and are followed by only digits can be interpreted as scientific notation (i.e., zero) and treated as equal. This issue falls under the Login Bypass vulnerability class. Users with certain "weird" passwords that produce magic hashes are particularly affected. Services relying on this logic are at risk of unauthorized access. Version 25.6.7 fixes the vulnerability.
Impacted products
Vendor Product Version
netalertx netalertx *



{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:netalertx:netalertx:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "CD0B1FF5-743B-4BE2-BF2A-942C62B99DF1",
              "versionEndExcluding": "25.6.7",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "NetAlertX is a network, presence scanner, and alert framework. Prior to version 25.6.7, a vulnerability in the authentication logic allows users to bypass password verification using SHA-256 magic hashes, due to loose comparison in PHP. In vulnerable versions of the application, a password comparison is performed using the `==` operator at line 40 in front/index.php. This introduces a security issue where specially crafted \"magic hash\" values that evaluate to true in a loose comparison can bypass authentication. Because of the use of `==` instead of the strict `===`, different strings that begin with 0e and are followed by only digits can be interpreted as scientific notation (i.e., zero) and treated as equal. This issue falls under the Login Bypass vulnerability class. Users with certain \"weird\" passwords that produce magic hashes are particularly affected. Services relying on this logic are at risk of unauthorized access. Version 25.6.7 fixes the vulnerability."
    },
    {
      "lang": "es",
      "value": "NetAlertX es un framework de red, esc\u00e1ner de presencia y alertas. Antes de la versi\u00f3n 25.6.7, una vulnerabilidad en la l\u00f3gica de autenticaci\u00f3n permit\u00eda a los usuarios eludir la verificaci\u00f3n de contrase\u00f1as mediante hashes m\u00e1gicos SHA-256 debido a una comparaci\u00f3n imprecisa en PHP. En versiones vulnerables de la aplicaci\u00f3n, se realiza una comparaci\u00f3n de contrase\u00f1as mediante el operador `==` en la l\u00ednea 40 de front/index.php. Esto genera un problema de seguridad: valores de \"hash m\u00e1gico\" especialmente manipulados, que se eval\u00faan como verdaderos en una comparaci\u00f3n imprecisa, pueden eludir la autenticaci\u00f3n. Debido al uso de `==` en lugar del estricto `===`, diferentes cadenas que comienzan con 0e y van seguidas solo de d\u00edgitos pueden interpretarse como notaci\u00f3n cient\u00edfica (es decir, cero) y tratarse como iguales. Este problema se enmarca en la vulnerabilidad de omisi\u00f3n de inicio de sesi\u00f3n. Los usuarios con ciertas contrase\u00f1as \"extra\u00f1as\" que generan hashes m\u00e1gicos se ven especialmente afectados. Los servicios que dependen de esta l\u00f3gica corren el riesgo de acceso no autorizado. La versi\u00f3n 25.6.7 corrige esta vulnerabilidad."
    }
  ],
  "id": "CVE-2025-48952",
  "lastModified": "2025-08-06T17:48:07.287",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "LOW",
          "baseScore": 9.4,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.5,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ]
  },
  "published": "2025-07-04T23:15:21.760",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "url": "https://github.com/jokob-sk/NetAlertX/security/advisories/GHSA-4p4p-vq2v-9489"
    },
    {
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "tags": [
        "Exploit",
        "Vendor Advisory"
      ],
      "url": "https://github.com/jokob-sk/NetAlertX/security/advisories/GHSA-4p4p-vq2v-9489"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-697"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.


Loading…

Loading…