CVE-2000-0762: The default installation of eTrust Access Control (formerly SeOS) uses a default encryption key, which allo...

Security readout for executives and security teams

Older installations of eTrust Access Control (formerly SeOS) shipped with a built-in encryption key that every customer received by default. Anyone who knew that key could impersonate the security administrator over the network and take control of protected systems. The issue affects default installs that were never hardened, and it is a legacy exposure from 2000 that should have been remediated long ago on any still-running host. Exposure is limited to legacy environments still running unhardened eTrust Access Control / SeOS deployments from around 2000. Modern estates should have no material exposure, but any surviving host with default keys and network-reachable admin services would allow spoofed administrator control. The bundle does not list specific vendor or version data, so scope must be confirmed against internal asset inventory. Low priority for most modern organizations because the product and vulnerability are from 2000. However, if any legacy eTrust/SeOS system remains in production, treat this as a high-priority remediation: default keys allow full administrative takeover, and the underlying access-control tier protects sensitive systems. Confirm scope with IT asset management before deprioritizing. Mitigation focus: Replace the default encryption key with a unique, strong key per the CA/Broadcom eTrust advisory.; Restrict network access to eTrust administrative services to trusted management hosts only.; Retire or upgrade any eTrust Access Control / SeOS installations still running legacy 2000-era builds..

Prepared

Jul 12, 2026, 00:03 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.