The code does not function according to its published specifications, potentially leading to incorrect usage.
When providing functionality to an external party, it is important that the product behaves in accordance with the details specified. When requirements of nuances are not documented, the functionality may produce unintended behaviors for the caller, possibly leading to an exploitable state.
Threat Mapped score: 0.0
Industry: Finiancial
Threat priority: Unclassified
CVE: CVE-2002-1446
Error checking routine in PKCS#11 library returns "OK" status even when invalid signature is detected, allowing spoofed messages.
CVE: CVE-2001-1559
Chain: System call returns wrong value (CWE-393), leading to a resultant NULL dereference (CWE-476).
CVE: CVE-2003-0187
Program uses large timeouts on unconfirmed connections resulting from inconsistency in linked lists implementations.
CVE: CVE-1999-1446
UI inconsistency; visited URLs list not cleared when "Clear History" option is selected.
N/A
N/A
| Phase | Note |
|---|---|
| Implementation | N/A |
Intro: In the following snippet from a doPost() servlet method, the server returns "200 OK" (default) even if an error occurs.
try { // Something that may throw an exception. ... } catch (Throwable t) { logger.error("Caught: " + t.toString()); return; }Intro: In the following example, an HTTP 404 status code is returned in the event of an IOException encountered in a Java servlet. A 404 code is typically meant to indicate a non-existent resource and would be somewhat misleading in this case.
try { // something that might throw IOException ... } catch (IOException ioe) { response.sendError(SC_NOT_FOUND); }