| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in RELIC. Affected is the function bn_get_prime. The manipulation of the argument Pos leads to integer overflow.
This vulnerability is traded as CVE-2023-36327. There is no exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in RELIC (affected version unknown). It has been rated as problematic. This issue affects the function bn_get_prime. The manipulation of the argument pos with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Integer Overflow vulnerability in RELIC before commit 421f2e91cf2ba42473d4d54daf24e295679e290e, allows attackers to execute arbitrary code and cause a denial of service in pos argument in bn_get_prime function.
The weakness was shared 09/01/2023 as 421f2e91cf2ba42473d4d54daf24e295679e290e. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-36327 since 06/21/2023. Technical details are known, but no exploit is available.
Applying the patch 421f2e91cf2ba42473d4d54daf24e295679e290e is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-40295). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 421f2e91cf2ba42473d4d54daf24e295679e290e
Timeline
06/21/2023 🔍09/01/2023 🔍
09/01/2023 🔍
01/13/2026 🔍
Sources
Advisory: 421f2e91cf2ba42473d4d54daf24e295679e290eStatus: Confirmed
CVE: CVE-2023-36327 (🔍)
GCVE (CVE): GCVE-0-2023-36327
GCVE (VulDB): GCVE-100-238589
EUVD: 🔍
Entry
Created: 09/01/2023 21:30Updated: 01/13/2026 19:05
Changes: 09/01/2023 21:30 (41), 09/29/2023 14:37 (11), 01/13/2026 19:05 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.