CVE-2023-31098 json
Apache InLong: Weak Password Implementation in InLong
published 2023-05-22 3 y ago modified 2026-09-10 1 mo ago also GHSA-w3wr-gmwf-r333 , EUVD-2023-2160
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Weak Password Requirements vulnerability in Apache Software Foundation Apache InLong.This issue affects Apache InLong: from 1.1.0 through 1.6.0.
When users change their password to a simple password (with any character or symbol), attackers can easily guess the user's password and access the account.
Users are advised to upgrade to Apache InLong's 1.7.0 or cherry-pick https://github.com/apache/inlong/pull/7805 https://github.com/apache/inlong/pull/7805 to solve it.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.inlong:manager-pojo | >=1.1.0, <1.47.0 |
1.47.0 |
Affected products
- Apache Software Foundation Apache InLong
- apache inlong
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
github.com
/apache/inlong/pull/7805
web
-
lists.apache.org
/thread/1fvloc3no1gbffzrcsx9ltsg08wr2d1w
vendor-advisory, web, mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2023-31098
advisory
-
github.com
/apache/inlong
package
Sources
- CVE List CVE-2023-31098
- GitHub Advisory GHSA-w3wr-gmwf-r333
- NVD CVE-2023-31098
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.