SShortSingh.
Back to feed

NocoBase Bug: Filtered Bulk Updates Ignore Conditions, Risk Data Corruption

0
·49 views

A code-level investigation into NocoBase 2.2.7 has revealed that bulk update operations do not carry filter conditions into the final SQL UPDATE statement. Instead, the platform first selects matching rows using the filter, then updates those rows by primary key alone — meaning rows that no longer meet the original condition at write time still get updated. The flaw was first reported on the official NocoBase forum on September 4th, with staff acknowledging they were investigating but no fix issued since. Testing on PostgreSQL 16 confirmed the behavior, with SQL logs showing the WHERE clause in the UPDATE containing only primary keys rather than the original filter. The vulnerability is rooted in the repository.ts update method, affects both available code paths, and poses a concurrency risk where stale or changed rows can be incorrectly overwritten.

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
ProgrammingHacker News ·

Jensen Huang says he is open to returning to his role, his first statement since resigning

Nvidia co-founder Jensen Huang has said he is open to returning to the company, according to a CNBC report. The remark marks his first public statement since he stepped down. The source material provided here contains only the headline and link metadata, so further details about the reasons for his resignation or the terms of any possible return could not be confirmed. Readers are encouraged to consult the original CNBC article for the full context.

0
ProgrammingDEV Community ·

Voice agent evaluators can be less reliable than the agents they grade

Rokas Remeika argues that regex-based scoring in voice agent evaluation pipelines introduces significant noise. Spontaneous speech often omits expected words, causing false negatives, while negated phrasing like "I would not say no" can trigger false refusal flags. These scoring errors can shift aggregate pass rates between evaluation runs even when the agent and model are unchanged. The author proposes a two-tier system that uses strict deterministic matching first, marking uncertain cases as unresolved, and escalates only those to an independent model for adjudication. He suggests practical checks, such as auditing unclassifiable transcripts and rerunning static batches under different scorer versions, to detect this instrument error.

0
ProgrammingDEV Community ·

Filter Toggle Causes 180 ms Interaction Delay and Layout Shift in Catalog Pages

A design-system pull request added a compact-density toggle to a catalog filter bar, but it caused problems on production pages despite working well in local testing. Telemetry showed the 75th-percentile Interaction to Next Paint on mid-tier Android devices rising from 38 ms to 180 ms, while Cumulative Layout Shift spiked to 0.14 as the sticky toolbar moved on each click. Investigation traced the cause to a root CSS variable update, an unstable context value object, and a layout effect that interleaved reads and writes, forcing repeated synchronous layouts. A React.memo hotfix did not help in production. The fix involved wrapping the grid filter update in a transition so the pressed chip could paint before the heavier reconciliation completed.

0
ProgrammingDEV Community ·

Researcher finds Windows 11 build flags coding agent use in optional telemetry

Security researcher Xusheng Li, who works on Binary Ninja, reports that one Windows 11 build keeps a daily yes-or-no flag indicating whether coding agents such as Codex, Claude Code and Copilot were seen running. His findings come from analysis of a single ARM64 virtual machine and Microsoft's documentation, and Microsoft had not commented at the time of reporting. According to Li, the component listens to events Windows already produces and records only which tracked program names appeared, not prompt text or source code. He found the resulting report in a diagnostics upload queue marked as optional, though he observed it being queued rather than leaving the machine. Li also noted that matching relies on executable names, meaning a renamed file could set a flag and a real agent under another name might go uncounted, and that the number of affected PCs is unknown.