The token kept its name and gained admin
A practitioner runs coding agents inside zones he draws by hand, and two low-rated Artifactory flaws are chained in the wild into an admin token that never changed its username.
How we Build
An agent in an old codebase works inside a map somebody drew by hand
Addy Osmani has written up how he runs coding agents in codebases older than the teams that own them. His unit is the zone. Green is well tested and isolated, yellow is mixed, and red is the authentication, billing and permissions code few people understand. Three rules turn that colouring into a procedure. A person draws the map, because an agent left to choose starts in the scariest file. A zone moves only when it is earned, once characterisation tests exist and the module’s owner has reviewed the agent’s first changes. And the zone fixes the verbs: green gets a tight loop, yellow gets tests first, red gets a human pairing on every step or no work at all.
Our position is that a person decides in advance where a machine may go.
An agent’s reach is a number somebody designed, not a paragraph somebody wrote.
Osmani got there from practice, not from method. His zones are the decision itself, taken once, by a named person, and revisited when the tests change. What is now better evidenced is the failure we had only argued for. An agent choosing its own starting point walks into the most dangerous file first, and he gives the reason: that file has the most interesting names in it. His account is one practitioner’s, drawn from commerce estates of five or six microsites.
How we Assure
Two flaws that grant nothing alone were chained into an admin token
Wiz Research has found three JFrog Artifactory vulnerabilities under exploitation in the wild. Two of them are dangerous in combination. The first returns an internal anonymous-user token to a caller who never authenticated, even where anonymous access is switched off. The second exchanges that token for one carrying admin scope, because Artifactory checks a token’s signature and its issuer without enforcing what the token is for. Neither grants administrative control by itself. Chained, they turn an unauthenticated request into an admin-scoped token, and the escalated token keeps the anonymous username while carrying admin authority. Wiz saw the pair used between 15 August and 8 September, followed by a Rust backdoor. 67 per cent of organisations running Artifactory held a vulnerable instance when the first was published. 59 per cent were still exposed six weeks later.
We tell a client that the damage a break-in does is set by whose credentials the intruder ends up holding.
Identity is the amplifier.
This is as clean a demonstration as that claim has had. Neither flaw looks interesting on the severity scale most firms patch by, which is why both sat while the critical one was fixed. That one was down from 67 per cent to 49 in a fortnight. The amplification happened in the identity layer, inside a token whose name never changed. What the research cannot tell us is how many of those exposed instances were reachable from outside at all. The figures count versions, so 67 per cent is probably a ceiling.