agpt 0.2.2 vulnerabilities

Known vulnerabilities in the agpt package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
H Server-side Request Forgery (SSRF) agpt is an An open-source attempt to make GPT-4 autonomous Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) through the `requests` wrapper. An attacker can manipulate the request process to access unauthorized data or interact with internal services by exploiting DNS rebinding vulnerabilities and redirect handling issues. How to fix Server-side Request Forgery (SSRF)? A fix was pushed into the `master` branch but not yet published.	[0,)
C Information Exposure agpt is an An open-source attempt to make GPT-4 autonomous Affected versions of this package are vulnerable to Information Exposure through the `request.py` wrapper. An attacker can intercept and misuse sensitive information by exploiting the improper handling of HTTP headers and cookies during redirects. Note: The standard requests library does not suffer from this vulnerability. When a redirect occurs, headers such as Authorization and Proxy-Authorization are not sent across origins, and cookies are managed securely using the standard cookiejar format. How to fix Information Exposure? A fix was pushed into the `master` branch but not yet published.	[0,)
M Information Exposure agpt is an An open-source attempt to make GPT-4 autonomous Affected versions of this package are vulnerable to Information Exposure due to missing access controls in the WebSocket API. Node execution updates were sent to any subscriber using a valid graph_id and graph_version, allowing unauthorized users to access another user's execution data either via shared Marketplace graphs or by subscribing with a known graph ID. Note: This is only exploitable if multiple users share access to the same instance. It does not affect separate platform instances or non-users. Single-user instances are not affected. For private instances with a user whitelist, the impact is limited to users approved by the administrator. How to fix Information Exposure? A fix was pushed into the `master` branch but not yet published.	[0,)

Vulnerability

Vulnerable Version

Server-side Request Forgery (SSRF)

agpt is an An open-source attempt to make GPT-4 autonomous

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) through the requests wrapper. An attacker can manipulate the request process to access unauthorized data or interact with internal services by exploiting DNS rebinding vulnerabilities and redirect handling issues.

How to fix Server-side Request Forgery (SSRF)?

A fix was pushed into the master branch but not yet published.

[0,)

Information Exposure

agpt is an An open-source attempt to make GPT-4 autonomous

Affected versions of this package are vulnerable to Information Exposure through the request.py wrapper. An attacker can intercept and misuse sensitive information by exploiting the improper handling of HTTP headers and cookies during redirects.

Note: The standard requests library does not suffer from this vulnerability. When a redirect occurs, headers such as Authorization and Proxy-Authorization are not sent across origins, and cookies are managed securely using the standard cookiejar format.

How to fix Information Exposure?

A fix was pushed into the master branch but not yet published.

[0,)

Information Exposure

agpt is an An open-source attempt to make GPT-4 autonomous

Affected versions of this package are vulnerable to Information Exposure due to missing access controls in the WebSocket API. Node execution updates were sent to any subscriber using a valid graph_id and graph_version, allowing unauthorized users to access another user's execution data either via shared Marketplace graphs or by subscribing with a known graph ID.

Note: This is only exploitable if multiple users share access to the same instance. It does not affect separate platform instances or non-users. Single-user instances are not affected. For private instances with a user whitelist, the impact is limited to users approved by the administrator.

How to fix Information Exposure?

A fix was pushed into the master branch but not yet published.

[0,)

agpt@0.2.2 vulnerabilities

An open-source attempt to make GPT-4 autonomous

latest version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?