A memory leak was detected in the function parse_mi_request while performing coverage-guided
fuzzing.
This issue can be reproduced by sending multiple requests of the following form:
{"jsonrpc": "2.0","method": "log_le
This malformed message was tested against an instance of OpenSIPS via FIFO transport layer and was
found to increase the memory consumption over time.
Impact
To abuse this memory leak, attackers need to reach the management interface which typically, should be
only exposed on trusted interfaces. In cases where the MI is exposed to the internet without authentication,
abuse of this issue will lead to memory exhaustion which may affect the underlying system’s availability. No
authentication is typically required to reproduce this issue.
On the other hand, memory leaks may occur in other areas of OpenSIPS where the cJSON library is used for parsing JSON objects.
Patches
The issue has been fixed in commit: 4175687.
References
Read more about this issue in the Audit Document section 3.14.
For more information
If you have any questions or comments about this advisory:
alfredfarrugia Analyst
sandrogauci Analyst
A memory leak was detected in the function
parse_mi_requestwhile performing coverage-guidedfuzzing.
This issue can be reproduced by sending multiple requests of the following form:
{"jsonrpc": "2.0","method": "log_leThis malformed message was tested against an instance of OpenSIPS via FIFO transport layer and was
found to increase the memory consumption over time.
Impact
To abuse this memory leak, attackers need to reach the management interface which typically, should be
only exposed on trusted interfaces. In cases where the MI is exposed to the internet without authentication,
abuse of this issue will lead to memory exhaustion which may affect the underlying system’s availability. No
authentication is typically required to reproduce this issue.
On the other hand, memory leaks may occur in other areas of OpenSIPS where the cJSON library is used for parsing JSON objects.
Patches
The issue has been fixed in commit: 4175687.
References
Read more about this issue in the Audit Document section 3.14.
For more information
If you have any questions or comments about this advisory: