<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 11:21:28 +0000</lastBuildDate>
    <item>
      <title>GHSA-wf8f-6423-gfxg — Jackson-core Vulnerable to Memory Disclosure via Source Snippet in JsonLocation</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wf8f-6423-gfxg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-core&lt;/p&gt;
&lt;p&gt;### Overview&lt;/p&gt;
&lt;p&gt;A flaw in Jackson-core&amp;#39;s `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible **information disclosure** in systems using **pooled or reused buffers**, like Netty or Vert.x.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability affects the creation of exception messages like:&lt;/p&gt;
&lt;p&gt;```
JsonParseException: Unexpected character ... at [Source: (byte[])...]
```&lt;/p&gt;
&lt;p&gt;When `JsonFactory.createParser(byte[] data, int offset, int len)` is used, and an error occurs while parsing, the exception message should include a snippet from the specified logical payload. However, the method `_appendSourceDesc` ignores the `offset`, and always starts reading from index `0`.&lt;/p&gt;
&lt;p&gt;If the buffer contains residual sensitive data from a previous request, such as credentials or document contents, that data may be exposed if the exception is propagated to the client.&lt;/p&gt;
&lt;p&gt;The issue particularly impacts server applications using:&lt;/p&gt;
&lt;p&gt;* Pooled byte buffers (e.g., Netty)
* Frameworks that surface parse errors in HTTP responses
* Default Jackson settings (i.e., `INCLUDE_SOURCE_IN_LOCATION` is enabled)&lt;/p&gt;
&lt;p&gt;A documented real-world example is [CVE-2021-22145](https://nvd.nist.gov/vuln/detail/CVE-2021-22145) in Elasticsearch, which stemmed from the same root cause.&lt;/p&gt;
&lt;p&gt;###…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: com.fasterxml.jackson.core:jackson-core&lt;/p&gt;
&lt;p&gt;### Overview&lt;/p&gt;
&lt;p&gt;A flaw in Jackson-core&amp;#39;s `JsonLocation._appendSourceDesc` method allows up to 500 bytes of unintended memory content to be included in exception messages. When parsing JSON from a byte array with an offset and length, the exception message incorrectly reads from the beginning of the array instead of the logical payload start. This results in possible **information disclosure** in systems using **pooled or reused buffers**, like Netty or Vert.x.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The vulnerability affects the creation of exception messages like:&lt;/p&gt;
&lt;p&gt;```
JsonParseException: Unexpected character ... at [Source: (byte[])...]
```&lt;/p&gt;
&lt;p&gt;When `JsonFactory.createParser(byte[] data, int offset, int len)` is used, and an error occurs while parsing, the exception message should include a snippet from the specified logical payload. However, the method `_appendSourceDesc` ignores the `offset`, and always starts reading from index `0`.&lt;/p&gt;
&lt;p&gt;If the buffer contains residual sensitive data from a previous request, such as credentials or document contents, that data may be exposed if the exception is propagated to the client.&lt;/p&gt;
&lt;p&gt;The issue particularly impacts server applications using:&lt;/p&gt;
&lt;p&gt;* Pooled byte buffers (e.g., Netty)
* Frameworks that surface parse errors in HTTP responses
* Default Jackson settings (i.e., `INCLUDE_SOURCE_IN_LOCATION` is enabled)&lt;/p&gt;
&lt;p&gt;A documented real-world example is [CVE-2021-22145](https://nvd.nist.gov/vuln/detail/CVE-2021-22145) in Elasticsearch, which stemmed from the same root cause.&lt;/p&gt;
&lt;p&gt;###…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wf8f-6423-gfxg</guid>
    </item>
  </channel>
</rss>
