CyberAlerts

How the FBI Catch Paedophiles | Inside The FBI

Description: How the FBI Catch Paedophiles | Inside The FBI

Source: DarkWebInformer

January 28th, 2025 (5 months ago)

Linux File System

Description: Linux File System

Source: DarkWebInformer

January 28th, 2025 (5 months ago)

Hackers exploiting flaws in SimpleHelp RMM to breach networks

Description: Hackers are believed to be exploiting recently fixed SimpleHelp Remote Monitoring and Management (RMM) software vulnerabilities to gain initial access to target networks. [...]

Source: BleepingComputer

January 28th, 2025 (5 months ago)

Phishing Campaign Baits Hook With Malicious Amazon PDFs

Description: In their discovery, researchers found 31 PDF files linking to these phishing websites, none of which have been yet submitted to VirusTotal.

Source: Dark Reading

January 28th, 2025 (5 months ago)

[@sentry/node] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

[@sentry/astro] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

[@sentry/aws-serverless] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

[@sentry/bun] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

[@sentry/google-cloud-serverless] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

[@sentry/nestjs] Potential DoS when using ContextLines integration

Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542...

Source: Github Advisory Database (NPM)

January 28th, 2025 (5 months ago)

Threat and Vulnerability Intelligence Database

Example Searches:

	How the FBI Catch Paedophiles \| Inside The FBI Description: How the FBI Catch Paedophiles \| Inside The FBI Source: DarkWebInformer January 28th, 2025 (5 months ago)
	Linux File System Description: Linux File System Source: DarkWebInformer January 28th, 2025 (5 months ago)
	Hackers exploiting flaws in SimpleHelp RMM to breach networks Description: Hackers are believed to be exploiting recently fixed SimpleHelp Remote Monitoring and Management (RMM) software vulnerabilities to gain initial access to target networks. [...] Source: BleepingComputer January 28th, 2025 (5 months ago)
	Phishing Campaign Baits Hook With Malicious Amazon PDFs Description: In their discovery, researchers found 31 PDF files linking to these phishing websites, none of which have been yet submitted to VirusTotal. Source: Dark Reading January 28th, 2025 (5 months ago)
	[@sentry/node] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)
	[@sentry/astro] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)
	[@sentry/aws-serverless] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)
	[@sentry/bun] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)
	[@sentry/google-cloud-serverless] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)
	[@sentry/nestjs] Potential DoS when using ContextLines integration Description: Impact The ContextLines integration uses readable streams to more efficiently use memory when reading files. The ContextLines integration is used to attach source context to outgoing events. The stream was not explicitly closed after use. This could lead to excessive amounts of file handles open on the system and potentially lead to a Denial of Service (DoS). The ContextLines integration is enabled by default in the Node SDK (@sentry/node) and SDKs that run in Node.js environments (@sentry/astro, @sentry/aws-serverless, @sentry/bun, @sentry/google-cloud-serverless, @sentry/nestjs, @sentry/nextjs, @sentry/nuxt, @sentry/remix, @sentry/solidstart, @sentry/sveltekit). Patches Users should upgrade to version 8.49.0 or higher. Workarounds To remediate this issue in affected versions without upgrading to version 8.49.0 and above you can disable the ContextLines integration. See the docs for more details. Sentry.init({ // ... integrations: function (integrations) { // integrations will be all default integrations return integrations.filter(function (integration) { return integration.name !== "ContextLines"; }); }, }); If you disable the ContextLines integration, you will lose source context on your error events. References Reported issue: https://github.com/getsentry/sentry-javascript/issues/14892 PR Fix: https://github.com/getsentry/sentry-javascript/pull/14997 References https://github.com/getsentry/sentry-javascript/security/advisories/GHSA-r5w7-f542... Source: Github Advisory Database (NPM) January 28th, 2025 (5 months ago)