filename stringlengths 5 36 | vulnerability stringclasses 43
values | description stringclasses 56
values | insecure_code stringlengths 11 347 |
|---|---|---|---|
ClientReceivingThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | serverSocket = new ServerSocket(listenPort); |
ClientReceivingThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | inStream = new ObjectInputStream(clientSocket.getInputStream()); |
ClientSendingThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | clientSocket = new Socket(destIP, destPort); |
ClientSide.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | Socket socket = new Socket("127.0.0.1", 13500); |
Communicator.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | ServerSocket serverMessageSocket = new ServerSocket(portNumberMessage); |
Communicator.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | ServerSocket serverStringSocket = new ServerSocket(portNumberString); |
ControlThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | loginServerSocket = new ServerSocket(loginListenPort); |
FileReceiveControlThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | inStream = new ObjectInputStream(serverComSocket.getInputStream()); |
FileReceiveControlThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | serverSocket = new ServerSocket(fileControlReceivePort); |
FileRequestHandlerThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | srcOIS = new ObjectInputStream(srcSocket.getInputStream()); |
FileRequestHandlerThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | destSocket = new Socket(destIP, destPort); |
FileRequestHandlerThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | destOIS = new ObjectInputStream(destSocket.getInputStream()); |
FileRequestListenerThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | serverSocket = new ServerSocket(fileRequestListenPort); |
FileSendControlThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | inStream = new ObjectInputStream(fileSendControlSocket.getInputStream()); |
FileSendControlThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | fileSendControlSocket = new Socket(serverIP, fileControlPort); |
FileSender.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | fileSenderSocket = new Socket(); |
ListenMessage.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | objStream = new ObjectInputStream(clientSocket.getInputStream()); |
ListenString.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | objStream = new ObjectInputStream(clientSocket.getInputStream()); |
LoginProcessThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | ois = new ObjectInputStream(remoteSocket.getInputStream()); |
LoginRequestThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | clientSocket = new Socket(destIP, destPort); |
LoginRequestThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | inStream = new ObjectInputStream(clientSocket.getInputStream()); |
LoginThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | ois = new ObjectInputStream(remoteSocket.getInputStream()); |
MessageReceiveWorkerThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | ois = new ObjectInputStream(clientSocket.getInputStream()); |
MessageReceiverThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | msgServerSocket = new ServerSocket(msgListenPort); |
NewFileReceiveThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | ObjectInputStream ois = new ObjectInputStream(socketChannel.socket() |
PendingMessageDeliveryThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | clientSocket = new Socket(destIP, msgPort); |
RegisterRequestThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | clientSocket = new Socket(destIP, destPort); |
RegisterRequestThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | inStream = new ObjectInputStream(clientSocket.getInputStream()); |
RequestProcessorThread.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | client = new Socket(destIP, msgPort); |
SendMessage.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | sendMessageSocket = new Socket(destIP, destPort); |
SendString.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | sendStringSocket = new Socket(destIP, destPort); |
ServerLoginListener.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | serverSocket = new ServerSocket(loginListenPort); |
ServerSide.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | ServerSocket serverSocket = new ServerSocket(13500); |
SimplerFileRequestHandlerThread.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | srcOIS = new ObjectInputStream(srcSocket.getInputStream()); |
Serialisering.java | java.lang.security.audit.object-deserialization.object-deserialization | Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data strea... | ObjectInputStream objektstrøm = new ObjectInputStream(datastrøm); |
DbToolsController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("tableview") |
DbToolsController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("refresh") |
DbToolsController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("modifydesc") |
DbToolsController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("code") |
DbToolsController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("generate") |
HomeController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("") |
SampleController.java | java.spring.security.unrestricted-request-mapping.unrestricted-request-mapping | Detected a method annotated with 'RequestMapping' that does not specify the HTTP method. CSRF protections are not enabled for GET, HEAD, TRACE, or OPTIONS, and by default all HTTP methods are allowed when the HTTP method is not explicitly specified. This means that a method that performs state changes could be vulnerab... | @RequestMapping("/") |
BufferUtil.fallback.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | var maskNum = mask.readUInt32LE(0, true); |
BufferUtil.fallback.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | var num = maskNum ^ source.readUInt32LE(i, true); |
BufferUtil.fallback.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | output.writeUInt32LE(num, offset + i, true); |
BufferUtil.fallback.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | var num = maskNum ^ data.readUInt32LE(i, true); |
BufferUtil.fallback.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | data.writeUInt32LE(num, i, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | this.length = this.frameHeader.readUInt16BE(2, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | this.frameHeader.readUInt32BE(2, true), |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | this.frameHeader.readUInt32BE(2+4, true) |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | this.closeStatus = this.binaryPayload.readUInt16BE(0, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | data.writeUInt16BE(this.closeStatus, 0, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | output.writeUInt16BE(this.length, outputPos, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | output.writeUInt32BE(0x00000000, outputPos, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | output.writeUInt32BE(this.length, outputPos + 4, true); |
WebSocketFrame.js | javascript.lang.security.detect-buffer-noassert.detect-buffer-noassert | Detected usage of noassert in Buffer API, which allows the offset the be beyond the end of the buffer. This could result in writing or reading beyond the end of the buffer. | this.maskBytes.writeUInt32BE(maskKey, 0, true); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.playerName, t->value->cstring); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.eventName, t->value->cstring); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.rank, t->value->cstring); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.points, t->value->cstring); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.progress, t->value->cstring); |
main.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp.clue, t->value->cstring); |
ADbg.h | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | return strncpy(prefix, string, MAX_PREFIX_LENGTH); |
BladeMP3EncDLL.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(lpszDate,__DATE__); |
BladeMP3EncDLL.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strncpy(lpszTemp,lpszDate,3); |
BladeMP3EncDLL.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy( pbeVersion->zHomepage, "http://www.mp3dev.org/" ); |
EST_error.c | c.lang.security.insecure-use-strcat-fn.insecure-use-strcat-fn | Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. | strcat(p, " - "); |
EST_error.c | c.lang.security.insecure-use-strcat-fn.insecure-use-strcat-fn | Finding triggers whenever there is a strcat or strncat used. This is an issue because strcat or strncat can lead to buffer overflow vulns. Fix this by using strcat_s instead. | strcat(p, msg); |
Festival.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | this(new Socket(addr, p), true); |
ImfName.h | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strncpy (_text, text, MAX_LENGTH); |
SocketsFile.java | java.lang.security.audit.crypto.unencrypted-socket.unencrypted-socket | Detected use of a Java socket that is not encrypted. As a result, the traffic could be read by an attacker intercepting the network traffic. Use an SSLSocket created by 'SSLSocketFactory' or 'SSLServerSocketFactory' instead. | s = new Socket(address, port); |
VbrTag.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strncpy(&pbtStreamBuffer[nBytesWritten], szVersion, 9); |
_cvhaartraining.h | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy( &(hf.desc[0]), desc ); |
amber.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strncpy(tracename, dir->d_name, PATH_MAX); |
ansi2knr.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(buf, more); |
audio_read.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strncpy (s, probe.charval, sizeof (long)); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"No Error"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Audio not initialized"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"audio_init called but audio allready initialized"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"audio sample size not 8 or 16"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Audio: Error getting shared memory segment"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Can not fork audio task"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Audio: Wrong read/write mode"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Audio: Buffer size for read too small"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Timeout waiting for audio initialization"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Buffer overflow writing audio"); |
audiolib.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(errstr,"Audio: Unknown error"); |
avio.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(uc->filename, filename); |
avio.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(proto_str, "file"); |
bootstrap.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(buffer + *buffer_size, string); |
bootstrap.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(temp_path, argv[current_arg]); |
bootstrap.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(out_path, argv[current_arg++]); |
brhist.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy ( Console_IO.str_up, "\033[A" ); |
brhist.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy ( Console_IO.str_up, tp ); |
brhist.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy ( Console_IO.str_clreoln, tp ); |
brhist.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy ( Console_IO.str_emph, tp ); |
brhist.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy ( Console_IO.str_norm, tp ); |
charset_test.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(s, "......."); |
charset_test.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy(s, ".."); |
codec.c | c.lang.security.insecure-use-string-copy-fn.insecure-use-string-copy-fn | Finding triggers whenever there is a strcpy or strncpy used. This is an issue because strcpy does not affirm the size of the destination array and strncpy will not automatically NULL-terminate strings. This can lead to buffer overflows, which can cause program crashes and potentially let an attacker inject code in the ... | strcpy( dest, src ); |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.