Asp Net
Monthly
Log-record suppression in the %aspnet-request pattern converter of Apache log4net lets an unauthenticated remote sender erase the log entry for their own request by placing markup such as <script> in a parameter, because reading HttpRequest.Params triggers ASP.NET request validation, throws HttpRequestValidationException inside the layout, and causes the appender to discard the entire event. Only applications running on ASP.NET for .NET Framework (the converter depends on System.Web, which netstandard/.NET Core lacks) with log4net 1.2.11 through 3.4.x and a layout that explicitly uses %aspnet-request are affected; versions from 3.5.0 onward are fixed. Impact is confined to the attacker suppressing logging of their own request - it cannot read data, delete other users' records, or crash the service - and there is no public exploit identified at time of analysis, no CISA KEV listing, and the assessed vector is AV:N/AC:L/PR:N/UI:N with only a low integrity impact (CVSS 5.3), making this a real but low-priority issue whose practical value is helping an attacker evade audit trails for a separate attack.
SQL injection in TCMAN GIM allows an authenticated low-privilege user to execute arbitrary SQL through the idmant GET parameter of /PC/frmEPIS.aspx, potentially reading, creating, updating, or deleting data in the underlying database. The issue affects GIM version 20250304 and earlier-EUVD records the affected range as GIM 0 <20250304-and remote exploitation requires a valid low-privilege session (CVSS PR:L) with no user interaction. A vendor patch is available, and no public exploit or CISA KEV entry was identified at time of analysis; EPSS is 0.04% (14th percentile), indicating low predicted exploitation activity.
Hospital Manager Backend Services prior to September 19, 2025 discloses verbose ASP.NET error pages to unauthenticated remote attackers when configured with customErrors mode='Off', enabling reconnaissance via framework/version metadata, stack traces, and internal paths. This low-to-moderate CWE-209 issue was remediated prior to that date, and no public exploit has been identified at time of analysis.
Log-record suppression in the %aspnet-request pattern converter of Apache log4net lets an unauthenticated remote sender erase the log entry for their own request by placing markup such as <script> in a parameter, because reading HttpRequest.Params triggers ASP.NET request validation, throws HttpRequestValidationException inside the layout, and causes the appender to discard the entire event. Only applications running on ASP.NET for .NET Framework (the converter depends on System.Web, which netstandard/.NET Core lacks) with log4net 1.2.11 through 3.4.x and a layout that explicitly uses %aspnet-request are affected; versions from 3.5.0 onward are fixed. Impact is confined to the attacker suppressing logging of their own request - it cannot read data, delete other users' records, or crash the service - and there is no public exploit identified at time of analysis, no CISA KEV listing, and the assessed vector is AV:N/AC:L/PR:N/UI:N with only a low integrity impact (CVSS 5.3), making this a real but low-priority issue whose practical value is helping an attacker evade audit trails for a separate attack.
SQL injection in TCMAN GIM allows an authenticated low-privilege user to execute arbitrary SQL through the idmant GET parameter of /PC/frmEPIS.aspx, potentially reading, creating, updating, or deleting data in the underlying database. The issue affects GIM version 20250304 and earlier-EUVD records the affected range as GIM 0 <20250304-and remote exploitation requires a valid low-privilege session (CVSS PR:L) with no user interaction. A vendor patch is available, and no public exploit or CISA KEV entry was identified at time of analysis; EPSS is 0.04% (14th percentile), indicating low predicted exploitation activity.
Hospital Manager Backend Services prior to September 19, 2025 discloses verbose ASP.NET error pages to unauthenticated remote attackers when configured with customErrors mode='Off', enabling reconnaissance via framework/version metadata, stack traces, and internal paths. This low-to-moderate CWE-209 issue was remediated prior to that date, and no public exploit has been identified at time of analysis.