An out-of-memory (OOM) issue in foxinmy/weixin4j
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 6.3epss 0.4%
exploitation probability
0.4%top 64% of all CVEs
observed exploitation
nono source reports it
In short
The weixin4j library can run out of memory due to improper handling of sequential memory allocation in its utility modules. This can cause applications using this library to crash or become unresponsive.
Technical detail
An improperly controlled sequential memory allocation vulnerability exists in the CharArrayBuffer and ClassUtil components of weixin4j-base, allowing unbounded memory consumption that can trigger out-of-memory (OOM) conditions. Exploitation requires sending crafted input that triggers excessive memory allocation; impact includes denial of service through application crash or resource exhaustion.
Summary generated and translated by AI from the official description.
Improperly Controlled Sequential Memory Allocation vulnerability in foxinmy weixin4j (weixin4j-base/src/main/java/com/foxinmy/weixin4j/util modules). This vulnerability is associated with program files CharArrayBuffer.Java, ClassUtil.Java.
This issue affects weixin4j.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:A/V:D/RE:M/U:Amber
Affected products
foxinmy · weixin4j