<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T14:57:14.589121+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-74879</id>
    <title>CVE-2026-74879 — openssl_encrypt before 1.4.0 Information Disclosure via /ready endpoint</title>
    <updated>2026-10-03T14:57:14.621576+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> jahlives openssl_encrypt</p>
<p>openssl_encrypt versions before 1.4.0 contain an information disclosure vulnerability in the /ready endpoint that returns full database exception strings to unauthenticated callers. Attackers can trigger database errors to extract sensitive information including hostnames, IP addresses, connection parameters, and potentially credentials from exception messages.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-74879"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-2vhw-q7vh-7xv2</id>
    <title>GHSA-2vhw-q7vh-7xv2 — openssl-encrypt's readiness endpoint leaks database error details to unauthenticated callers</title>
    <updated>2026-10-03T14:57:14.621645+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: openssl-encrypt</p>
<p>### Summary</p>
<p>The `/ready` endpoint in `openssl_encrypt_server/server.py` at **lines 159-175** catches database errors and returns the full exception string in the response.</p>
<p>### Affected Code</p>
<p>```python
except Exception as e:
    return {"status": "not_ready", "reason": str(e)}
```</p>
<p>### Impact</p>
<p>Database exception messages can leak:
- Database hostnames and IP addresses
- Connection parameters and port numbers
- Driver version information
- Potentially database credentials if included in connection string errors</p>
<p>This information is available to unauthenticated callers.</p>
<p>### Recommended Fix</p>
<p>- Return a generic error message: `{"status": "not_ready", "reason": "database unavailable"}`
- Log the full exception server-side for debugging</p>
<p>### Fix</p>
<p>Fixed in commit `7aa8787` on branch `releases/1.4.x` — replaced str(e) with generic "database check failed" message; full exception logged server-side at WARNING level.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-2vhw-q7vh-7xv2"/>
  </entry>
</feed>
