dbcve.org
Sap R 3Application · Sap

CVE-2002-1577

HIGH · 7.5 CVSS v2.0 Published 2004-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SAP R/3 2.0B to 4.6D installs several clients with default users and passwords, which allows remote attackers to gain privileges via the (1) SAP*, (2) SAPCPIC, (3) DDIC, (4) EARLYWATCH, or (5) TMSADM accounts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SAP R/3 versions 2.0B through 4.6D ship with multiple default user accounts (SAP*, SAPCPIC, DDIC, EARLYWATCH, TMSADM) that retain factory-set default passwords. Remote attackers can authenticate to these accounts without credentials by using the known default passwords, gaining elevated privileges within the SAP system.

MitigationImmediately change passwords for all default accounts to strong, unique values or disable accounts not required for operations. Restrict network access to SAP ports (3200, 3300, 3600, 8000, etc.) to prevent unauthorized remote authentication attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sap R 3Application
Affected:= 2.0b_to_4.6d

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed SAP R/3 version
    Query the SAP system for its version using transaction code SM51 or check the SAP system information via sapinfo command. Compare the version string against the affected range 2.0B through 4.6D.
    Affected if The installed version falls within 2.0B to 4.6D inclusive.
  2. Enumerate default SAP user accounts
    Use SAP transaction code SU01 or USR02 table query to list user accounts. Check for the presence of accounts: SAP*, SAPCPIC, DDIC, EARLYWATCH, and TMSADM.
    Affected if Any of these default accounts exist in the SAP user master records.
  3. Verify default account password status
    Attempt to log in using each default account with its known default password. Common default passwords include: PASS for SAP*, SAPCPIC for SAPCPIC, 19920706 for DDIC, and WATCH for EARLYWATCH. Alternatively, use transactioncode SU01 to inspect whether passwords remain at factory-set values.
    Affected if Any default account accepts its factory-set password for authentication.
  4. Check default account status and lock configuration
    Use transaction code SU01 or USR02 to examine whether these default accounts are locked (USTART = 'L') or still active. Check the LOGONDAYS and LOGONTIME restrictions.
    Affected if Default accounts are unlocked and have no password change requirement flags set.
  5. Assess network exposure of SAP ports
    Use network scanning tools (such as netstat, nmap, or port scanners) to determine if SAP ports 3200, 3300, 3600, 8000, and related dispatcher ports are exposed to untrusted networks or the internet.
    Affected if SAP ports are accessible from network segments outside the trusted internal environment.

A system is affected if it runs SAP R/3 version 2.0B through 4.6D and has any default accounts (SAP*, SAPCPIC, DDIC, EARLYWATCH, TMSADM) still active with default passwords accessible from the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change passwords for all default accounts to strong, unique values or disable accounts not required for operations. Restrict network access to SAP ports (3200, 3300, 3600, 8000, etc.) to prevent unauthorized remote authentication attempts.

Fix this in Sap R 3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-1577 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-1577 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data