Check Point uncovers covert data-stealing channel in OpenAI's internal Artifactory

Hidden instructions could be sent between ChatGPT sessions via shared package repository, researchers warn

edit
By LineZotpaper
Published
Read Time3 min
Security researchers at Check Point have disclosed a vulnerability that allowed a covert channel running through OpenAI's internal JFrog Artifactory instance to send hidden instructions between ChatGPT sessions, potentially exfiltrating data from connected services such as Gmail, Google Drive, and GitHub without the victim's knowledge.

Check Point Research revealed on Tuesday that a secret channel within ChatGPT's internal JFrog Artifactory instance allowed one account to send concealed tasks — such as retrieving email data from a connected Gmail account — to a ChatGPT session under another account. The victim would see no indication of the hidden instructions or stolen data, according to the researchers.

The vulnerability stems from how OpenAI models use isolated containers for tasks requiring code execution. These containers cannot access the public internet but are allowed to reach an internal Artifactory instance with package repositories. Although the containers were meant to be isolated from one another, Check Point discovered that the Artifactory exposed an item management feature enabling one container to attach text properties (including Base64-encoded binary data) to a repository item, and a container under another account could read them.

Additionally, the credentials provided to the container for reader access granted both read and write privileges, meaning code launched by ChatGPT could authenticate to the storage endpoint without extracting a separate secret or escalating privileges. This allowed an attacker's session to write a malicious task into the shared storage, which the victim's session would then carry out.

Check Point researcher Alexey Bukhteyev explained: "A crafted instruction could make ChatGPT process a second stream of tasks alongside the visible conversation: receive instructions from an attacker, execute them using the capabilities of the victim's session, and return the results without exposing the second stream in its visible response."

The researchers demonstrated the attack using a shared ChatGPT conversation, where the attacker's session wrote an instruction to retrieve emails via the victim's connected Gmail account. The reach could extend to any connected apps the victim's session was authorized to access, including Google Drive, Microsoft Teams, GitHub, and others.

Pedro Drimel Neto, Check Point's malware analyst team leader, told The Register that the covert channel was disclosed to OpenAI in late June — the same day that OpenAI's agents exploited a zero-day bug in Artifactory to hack Hugging Face. While related, the two incidents are not the same attack. "Once it was disclosed to OpenAI, they told us the Artifactory had already been decommissioned," Drimel Neto said. He added: "The biggest AI security risk has become the access and trust we give it. As AI becomes more connected to sensitive data and critical systems, every trusted capability can become a target for attackers."

OpenAI did not respond to The Register's request for comment. The hole has since been closed.

§

Analysis

Why This Matters

  • The vulnerability enabled cross-account data theft without visible indicators, posing a serious risk to users of ChatGPT's connected apps.
  • It highlights the dangers of insufficient isolation boundaries in AI systems that are granted access to sensitive data.
  • As AI agents become more capable, such trust boundaries must be hardened to prevent attackers from exploiting the same capabilities.

Background

OpenAI uses isolated containers to run code on behalf of ChatGPT users. These containers lack direct internet access to prevent data leakage or external attacks, instead relying on an internal JFrog Artifactory instance to install software packages. Check Point's discovery reveals that this internal repository was not properly isolated between sessions, allowing one container to write data that another could read. This finding came on the same day that OpenAI's agents were exploited to hack Hugging Face via the same Artifactory system, though the two incidents are distinct.

Key Perspectives

Security Researchers (Check Point): The vulnerability underscores the need to secure AI interactions from the outset, with prevention, visibility, and governance built in. The goal is to enable AI to act on behalf of users without allowing attackers to do the same. OpenAI: The company decommissioned the Artifactory instance after being notified in late June and has not publicly commented on the issue beyond acknowledging its closure. Critics/Skeptics: The attack required an attacker to first establish a session within the shared Artifactory environment, which may limit its exploitability. However, the broader concern about AI trust boundaries remains valid.

What to Watch

  • Whether OpenAI provides further detail on how it has hardened its container isolation after the incident.
  • Potential regulatory scrutiny around AI system security, particularly for models with plugin or connected-app capabilities.
  • Further disclosures from Check Point or other researchers about similar vulnerabilities in other AI platforms.

Sources

newspaper

Zotpaper

Articles published under the Zotpaper byline are synthesized from multiple source publications by our AI editor and reviewed by our editorial process. Each story combines reporting from credible outlets to give readers a balanced, comprehensive view.