Tag: Errors

Problems with application errors

ID	Title	Description	Category	Technology	Tags
prequel-2025-0011 Medium Impact: 7/10 Mitigation: 5/10	GraphQL internal server error due to record not found	The application is experiencing internal server errors when GraphQL operations attempt to access records that do not exist in the database. This occurs when GraphQL queries reference entities that have been deleted, were never created, or are inaccessible due to permission issues. Instead of handling these cases gracefully with proper error responses, the API is escalating them to internal server errors that may impact client applications and user experience.	GraphQL Problems	graphql	GraphQL Database Errors
prequel-2025-0012 Medium Impact: 6/10 Mitigation: 5/10	GraphQL internal server error due to unhandled exception in NestJS resolver	The application is generating internal server errors during GraphQL operations due to uncaught exceptions in resolver logic. These errors are not properly handled or transformed into structured GraphQL responses, resulting in unexpected 500-level failures for client applications. Stack traces often reference NestJS internal files like `external-context-creator.js`, indicating the framework attempted to execute resolver logic but encountered an exception that was not intercepted by the application code.	GraphQL Problems	graphql	GraphQL Errors nestjs
prequel-2025-0013 Critical Impact: 9/10 Mitigation: 6/10	Deployment Replica OOM Caused HTTP 500 Error	A deployment replica OOM caused HTTP 500 error.	Memory Problems	oom	OOM Errors
prequel-2025-0014 Medium Impact: 2/10 Mitigation: 3/10	Jetty IllegalStateException	A session object in an application thread is possibly being accessed outside the scope of a request.	Jetty Problems	jetty	Jetty Exceptions Errors
prequel-2025-0017 Medium Impact: 3/10 Mitigation: 4/10	Jetty HTTP 500 Errors	A Jetty HTTP 500 error occurred.	Jetty Problems	jetty	Jetty Errors