SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

CERT-In Flags 14 High-Severity ISC BIND Vulnerabilities Across Multiple Releases

0
·15 views

India's CERT-In issued advisory CIVN-2026-0467 on 21 September 2026, identifying 14 high-severity vulnerabilities in ISC BIND across a wide range of versions from 9.11.0 through 9.21.25. The flaws span three weakness categories: memory-safety issues that can crash resolvers, resource-consumption bugs that degrade performance, and trust-boundary flaws that may cause DNS servers to return incorrect answers. No active exploitation of any of the 14 CVEs has been reported by CERT-In at this time. Affected operators are advised to update to fixed builds listed in ISC's official advisory index and to restrict resolver exposure by limiting recursion, requiring TSIG for transfers, and rate-limiting DNS-over-HTTPS. With over 19 million internet-facing assets fingerprinted as ISC BIND by ZoomEye, the potential attack surface is considered significant.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Claude Code 'Don't Ask Again' feature linked to passwords exposed in 1,122 public GitHub files

A report highlighted that Claude Code's 'Don't Ask Again' feature, intended to remember user preferences and reduce repetitive prompts, was associated with sensitive credentials appearing in 1,122 public GitHub files. The article frames the issue as a security lapse arising from prioritizing convenience over protection. The author draws on a personal experience of accidentally publishing API keys to illustrate the risk. Recommended safeguards include storing secrets in environment variables, conducting code reviews, and using GitHub Secrets to keep sensitive data out of repositories. The piece emphasizes that developers should remain vigilant about what they publish.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

NVKE: Open Source Tool for Running Managed GPU Kubernetes Clusters on Your Own Hardware

NVIDIA Kubernetes Engine (NVKE) is an open source, Apache-2.0 licensed project that lets platform teams create and operate isolated Kubernetes clusters on bare-metal GPU servers they own. It runs as a management plane on the hardware and provisions machines through NVIDIA Infra Controller, with each workload cluster getting its own control plane, etcd and node pools. Users interact with their clusters using standard kubectl, without needing to know NVKE exists. The project is currently in preview, its APIs may change between releases, and it is not recommended for production workloads. It is aimed mainly at organizations building internal Kubernetes-as-a-service offerings on GPU infrastructure.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why RunPod checkpoints vanish after a pod stops, and how to keep them

Users running training jobs on RunPod have reported that model checkpoints disappeared after they stopped the pod to save money, often without any error message. The cause is that default output paths and the Hugging Face cache sit on container storage, which is wiped when a pod stops or terminates, while only a network volume mounted at /workspace persists. The article recommends explicitly setting the checkpoint output directory to /workspace and exporting HF_HOME to a persistent path in the launch script. Eight user research sessions with ML engineers found checkpoint loss to be the most consistently reported failure. The author also suggests running a pre-flight storage check, such as the open-source ComputeFence tool, before a job begins.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Classroom Session Shutdown: Revoke Tokens Before Channel Cleanup and Attendance Logging

The article argues that a classroom's in-app notification channel should be shut down in a fixed order: revoke issued tokens, disconnect remaining clients, then delete the channel. It recommends that a Node.js Express application handle this as one shutdown operation that also records the session end time for attendance reporting. Revoking tokens first prevents clients from reconnecting and recreating state, while deleting the channel first would leave them retrying. The piece also stresses tracking each shutdown step with identifiers so responders can tell an incomplete shutdown from a finished one followed by rejected reconnects. It separates a student's temporary connection loss from a teacher ending the class, and presents the instrumentation as a proposed design rather than a built-in provider feature.

0 comments Read more at DEV Community