OpenAI Monorepo Breached via Unpatched Library and SSO Flaw, Not AI Exploit

·14 views

Three white-hat researchers — Harsh Jaiswal, Mohan Pedhapati, and Rahul Maini — gained access to OpenAI's internal code repository in July 2025 through a chain of two ordinary software vulnerabilities. The breach exploited a missing Debian security backport in the libheif image-decoding library used by Discourse, the software powering OpenAI's community forum, combined with an SSO misconfiguration that granted excessive trust to that forum. The researchers used a Claude AI model to assist in crafting the exploit, but the AI reduced effort rather than introducing a novel attack category. After reaching the private monorepo, the team opened a single harmless pull request to prove access, read no sensitive code, and promptly reported the findings via OpenAI's Bugcrowd bug bounty program. OpenAI confirmed a fix within roughly 14 hours of the submission, Discourse published a security advisory, and the researchers were awarded $6,500 for the OpenAI-side finding.

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)

Common coturn TURN Server Misconfigurations That Silently Break WebRTC Relays

Self-hosting a TURN server with coturn is a frequent last resort for WebRTC developers, but several common misconfigurations can cause silent failures that are difficult to diagnose. On Debian and Ubuntu systems, the coturn package ships with its enable switch commented out in /etc/default/coturn, meaning the service can appear active via systemctl while never actually binding to any port. Developers can verify whether coturn is truly running by checking bound ports with 'ss -lunp' rather than relying on service status alone. A separate issue arises when cloud VMs advertise private internal IP addresses as relayed candidates, causing ICE negotiation to stall even though allocations appear successful server-side. Before assuming coturn itself is broken, engineers should first confirm TURN is actually in the connection path using browser WebRTC diagnostic tools and rule out unroutable addresses or closed UDP port ranges, which produce identical symptoms and are far more common.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Only 1 in 4 'Remote' Jobs Truly Open to India, Developer's Script Finds

A developer scraped around 900 job postings across eight remote job boards to determine how many were genuinely accessible to applicants based in India. After filtering for React, Node, and full-stack roles posted within 14 days, 71 relevant listings were identified. Of those, 41 were restricted by geography, timezone, or work-authorization requirements, leaving only 16 truly open to Indian applicants. The developer built the tool — now available as an open-source scraper on Apify — to automatically classify each posting using location fields, description phrases, timezone rules, and local-hire markers. The project supports over 110 countries and can also function as an MCP tool for AI agents.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

What Is a Harness? The Software Layer That Makes LLMs Actually Useful

A harness is a software layer that wraps around a large language model (LLM), responsible for constructing prompts and translating the model's responses into executable actions. Because LLMs have no built-in memory, the harness must compile and resend the entire conversation history — along with system instructions and available tools — with every new user interaction. Products like ChatGPT, Claude Code, and Cursor all implement their own harness engineering around underlying models. For end users, this architecture means that longer, topic-mixed conversations can increase the risk of the model producing inaccurate responses. For developers building AI-integrated applications, managing this context window — deciding what information to include, how to structure it, and how to handle the model's output — becomes a core engineering responsibility.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

agent-usage Tool Tracks AI Agent Costs After Uncapped 5-Hour Spending Runs

A new open-source tool called agent-usage addresses a key problem where AI agents spawning sub-agents can consume hours of compute time with no cost estimate or user confirmation. The tool provides a local dashboard that breaks down usage by agent, billing domain, and model. It is available via npm as agent-usage-all-in-one and runs on macOS with Node 24 or higher. The project is MIT-licensed and hosted on GitHub, offering local charts and advisory insights without any automatic intervention. A menubar interface is listed on the roadmap but has not yet been released.

0 comments Read more at DEV Community