Description

iFlytek astron-agent through 1.1.1 contains an authorization bypass vulnerability in the copyFlow endpoint that fails to validate workflow ownership. Authenticated attackers can enumerate workflow identifiers and overwrite other tenants' workflows or copy private workflows to read their definitions.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.1",
  "pubDate": "2026-08-29T17:18:00.057Z",
  "pubdate": "2026-08-29T17:18:00.057Z",
  "executiveSummary": "iFlytek astron-agent versions through 1.1.1 are susceptible to an authorization bypass vulnerability located within the copyFlow endpoint.\nThis flaw stems from a critical failure in the application's access control logic, specifically regarding the validation of workflow ownership during copy operations.\nThe vulnerability allows authenticated attackers to perform unauthorized actions across multi-tenant boundaries, including the enumeration of workflow identifiers and the manipulation of workflows belonging to other tenants.\nBy exploiting this flaw, an attacker can overwrite the integrity of existing workflows or perform data exfiltration by copying private workflow definitions to their own account.\nThe risk is significant due to the potential for unauthorized data disclosure and the disruption of business process automation within the affected environment.\nSuccessful exploitation requires the attacker to hold an authenticated session within the application, though no elevated administrative privileges are necessary to conduct the attack.",
  "technicalDetails": "The vulnerability exists in the copyFlow endpoint of the iFlytek astron-agent software, affecting all versions up to and including 1.1.1.\nThe root cause is an insecure direct object reference (IDOR) condition combined with a lack of server-side ownership verification. When a request is made to the copyFlow endpoint, the application fails to verify whether the authenticated user possesses sufficient permissions or legal ownership of the specified workflow identifier (ID).\nAn attacker can systematically enumerate workflow IDs through sequential scanning or metadata analysis. Since the endpoint does not enforce tenant isolation or ownership checks, providing an arbitrary, valid workflow ID from a different tenant context allows the application to execute the copy operation as if the requester were the legitimate owner.\nThe exploitation flow is as follows: 1) The attacker authenticates to the target instance of astron-agent. 2) The attacker intercepts or reconstructs a request targeting the copyFlow endpoint. 3) The attacker modifies the target workflow identifier parameter to correspond with a workflow belonging to a separate, private tenant. 4) The server processes the request without validating the relationship between the authenticated user's session token and the requested resource's owner metadata. 5) The application completes the action, either by overwriting the target resource with malicious payload content or by duplicating a private workflow definition into the attacker's personal workspace for subsequent analysis and data theft.\nThis vulnerability effectively bypasses multi-tenancy logical boundaries, allowing for cross-tenant unauthorized data access and integrity compromise. Because the endpoint is reachable via the primary application interface, it remains exposed to any authenticated user within the system, making it a critical threat to internal data privacy and business process integrity."
}