CVE-1999-0254: Critical severity Sun Solaris vulnerability

Published Nov 2, 1998
·
Updated

A hidden SNMP community string in HP OpenView allows remote attackers to modify MIB tables and obtain sensitive information.

Affected Software

1 affected component
Sun Solaris=2.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Remove any hidden or default SNMP community strings in HP OpenView and replace them with a strong, unique community string. Ensure no undocumented community strings remain configured.

    HP OpenView (SNMP) on Oracle Solaris / ZFS hosts SNMP community string = remove hidden/default; set to a strong unique community string
  2. Configuration

    Disable the SNMP service in HP OpenView if it is not required for management or monitoring.

    HP OpenView SNMP service = disabled if not required
  3. Compensating control

    Restrict access to SNMP management interfaces to trusted hosts/IP ranges using network controls (firewall, ACLs, or management network isolation) to limit exposure of SNMP community strings.

  4. Operational

    Audit MIB tables and HP OpenView logs for unauthorized modifications, and assume sensitive information may have been exposed. Rotate any credentials, community strings, or keys that may have been disclosed and review affected systems for compromise.

Event History

Nov 2, 1998
CVE Published
05:00 AM
Data Sourced
via NVD·05:00 AM
DescriptionSeverityAffected Software
Feb 4, 2000
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-1999-0254?

CVE-1999-0254 is considered a medium severity vulnerability due to its potential to expose sensitive information.

2

How do I fix CVE-1999-0254?

To fix CVE-1999-0254, ensure that SNMP community strings are secured and not left hidden or vulnerable.

3

What software is affected by CVE-1999-0254?

CVE-1999-0254 specifically affects HP OpenView running on Oracle Solaris 2.6.

4

What are the risks associated with CVE-1999-0254?

The risks of CVE-1999-0254 include unauthorized modification of MIB tables and leakage of sensitive information to attackers.

5

Is CVE-1999-0254 still relevant today?

Yes, CVE-1999-0254 remains relevant as it highlights vulnerabilities in SNMP configurations that can still be exploited in legacy systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203