Search: probes.space
3 threats
Most recently published first
| Severity | CVSS | Signals | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|---|
| Low | 3.7 | EPSS 0.2% | CVE-2026-44687NLnet Labs Unbound · Off-by-one Error Low3.7EPSS 0.2%CVE Database V5CVE-2026-44687 In NLnet Labs Unbound 1.13.2 up to and including 1.25.1, stub or forward zones where the name is below an intermediate labed below a DNSSEC signed zone could be shadowed by the intermediate label's secure NXDOMAIN answer from the parent. This is caused by an off-by-one error in 'harden-below-nxdomain' logic; enabled by default. It effectively bypasses the configuration and the configured stub/forward zone is never contacted. 'harden-below-nxdomain' does an upward DNS cache walk together with a delegation point guard that does not allow NXDOMAIN synthesis above stub/forward zones. The guard tests the domain name but before stripping a label. This results in an iteration where the domain name equals the configured stub/forward zone apex that passes the guard, strips one more label, and probes the cache at the apex's immediate public parent. If that parent has a cached DNSSEC-secure NXDOMAIN, which it will for any private namespace nested two or more labels under a signed public name, the walk returns it and the configured stub/forward upstream is never contacted. This can only be triggered by the query for the intermediate label (between the stub/forward apex and the DNSSEC parent zone). | CVE Database V5 | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f3f4ff9ea00766589ae9dece7648aa4ce29ac9bc82173fce0a1adefaeb6c8f5a) ue-jenkins-buildkite@99999.0.0 is a dependency-confusion package targeting an internal Epic Games / Unreal Engine CI namespace (name evokes Jenkins/Buildkite tooling; version 99999.0.0 is the canonical shape used to win private-registry resolution). Its package.json preinstall script runs automatically on npm install and performs installer-side credential harvest: it collects os.hostname(), username, cwd, platform, and arch; probes CI-specific environment variables (HORDE_AGENT, GITHUB_ACTIONS, JENKINS_URL, TEAMCITY_VERSION); and enumerates process.env filtering by the regex /^(AWS_|GITHUB_|GH_|NPM_|EPIC_|UE_|HORDE_|P4|CI|BUILD|TOKEN|KEY|SECRET)/i, taking up to 30 matching variables. The collected data is POSTed as JSON over plain HTTP to the bare-IP endpoint http://109.123.247.172/npm/ue_jenkins_buildkite, and an out-of-band DNS beacon is issued to <host>-<user>.ue_jenkins_buildkite.npm.epic-dc.oast.fun. The regex is a credential-shaped bulk scraper (AWS keys, GitHub tokens, npm publish tokens, generic *TOKEN*/*KEY*/*SECRET* variables) unrelated to any legitimate build-tool license check. ## Source: ghsa-malware (55fd457fdd033f752d6550cdd66a9f0d98348f07c118af4e5f75a4eb9948b7d2) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (a67a3300cb2357e9661889459167d34c43be7925bd3d476d3a08588d9a907b59) The OpenSSF Package Analysis project identified 'ue-jenkins-buildkite' @ 99999.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. | GCVE Database | |||
| Medium | 4.4 | EPSS 0.1% | CVE-2026-35233Oracle Linux dtrace · Out-of-bounds Read Medium4.4EPSS 0.1%CVE Database V5CVE-2026-35233 An unprivileged attacker can craft a user-space process with a malicious ELF binary containing an out-of-range sh_link field. When root-level dtrace attaches to -- or instruments -- that process (via dtrace -p , pid probes, or USDT), the ELF parser reads heap memory beyond the allocated section cache array without any bounds check. This results in an uninitialized/out-of-bounds heap read that can cause a NULL pointer dereference crash of the dtrace process (DoS), or -- depending on heap layout -- a read-then-use of a garbage pointer controlled by adjacent allocations, providing a foothold toward further exploitation in a privileged context. | CVE Database V5 |
Page 1 of 1