From abdeaabd779ebd0ba8cc4bf0e37c9b0aa8dc28ce Mon Sep 17 00:00:00 2001
From: ihsinme <61293369+ihsinme@users.noreply.github.com>
Date: Wed, 6 Jan 2021 22:46:03 +0300
Subject: [PATCH] Update MemoryLeakOnFailedCallToRealloc.ql

---
 .../Security/CWE/CWE-401/MemoryLeakOnFailedCallToRealloc.ql   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/cpp/ql/src/experimental/Security/CWE/CWE-401/MemoryLeakOnFailedCallToRealloc.ql b/cpp/ql/src/experimental/Security/CWE/CWE-401/MemoryLeakOnFailedCallToRealloc.ql
index c425ed76bc0..5ec4af3b4ce 100644
--- a/cpp/ql/src/experimental/Security/CWE/CWE-401/MemoryLeakOnFailedCallToRealloc.ql
+++ b/cpp/ql/src/experimental/Security/CWE/CWE-401/MemoryLeakOnFailedCallToRealloc.ql
@@ -1,13 +1,13 @@
 /**
  * @name Memory leak on failed call to realloc
  * @description The expression mem = realloc (mem, size) is potentially dangerous, if the call fails, we will lose the pointer to the memory block.
- *	            An unsuccessful call is possible not only when trying to allocate a large amount of memory, but also when the process memory is strongly segmented.
  *              We recommend storing the result in a temporary variable and eliminating memory leak.
  * @kind problem
  * @id cpp/memory-leak-on-failed-call-to-realloc
  * @problem.severity warning
  * @precision medium
- * @tags security
+ * @tags correctness
+ *       security
  *       external/cwe/cwe-401
  */