CVE-2002-2301
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames...
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames and passwords in a world-readable file, which allows local users to read the passwords and log onto the database.
Exploit likelihood
What each source reports
NVD Score used
3.3
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames and passwords in a world-readable file, which allows local users to read the passwords and log onto the database.
- Record
CVE-2002-2301- CVSS 2.0
- 3.3 Low
AV:L/AC:M/Au:N/C:P/I:P/A:N - Weakness
- CWE-255
- Updated
- 2026-11-02
CVE List No score
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames and passwords in a world-readable file, which allows local users to read the passwords and log onto the database.
- Record
CVE-2002-2301- Updated
- 2026-11-02
EUVDEUVD-2002-2279 No score
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames and passwords in a world-readable file, which allows local users to read the passwords and log onto the database.
- Record
EUVD-2002-2279- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-37gf-vc2r-h3rw No score
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames...
Lawson Financials 8.0, when configured to use a third party relational database, stores usernames and passwords in a world-readable file, which allows local users to read the passwords and log onto the database.
- Record
GHSA-37gf-vc2r-h3rw- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2002-2301 is a low vulnerability (CVSS 3.3) in Lawson Software Financials, published December 31, 2002. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.27%, the 19th percentile. No source names a fixed version.