mina2 - Debian Package Tracker

general

source: mina2 (main)
version: 2.2.1-3
maintainer: Debian Java Maintainers (archive) (DMD)
uploaders: Emmanuel Bourg [DMD]
arch: all
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.0.19-2
oldstable: 2.1.4-2
stable: 2.2.1-3
testing: 2.2.1-3
unstable: 2.2.1-3

versioned links

2.0.19-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.1.4-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libmina2-java

action needed

A new upstream version is available: 2.2.4 high

A new upstream version 2.2.4 is available, you should consider packaging it.

Created: 2023-06-09 Last update: 2025-01-21 00:03

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2024-52046: The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods: /** * Accept class names where the supplied ClassNameMatcher matches for * deserialization, unless they are otherwise rejected. * * @param classNameMatcher the matcher to use */ public void accept(ClassNameMatcher classNameMatcher) /** * Accept class names that match the supplied pattern for * deserialization, unless they are otherwise rejected. * * @param pattern standard Java regexp */ public void accept(Pattern pattern) /** * Accept the wildcard specified classes for deserialization, * unless they are otherwise rejected. * * @param patterns Wildcard file name patterns as defined by * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch} */ public void accept(String... patterns) By default, the decoder will reject *all* classes that will be present in the incoming data. Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.

Created: 2024-12-26 Last update: 2025-01-14 11:30

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2024-52046: The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods: /** * Accept class names where the supplied ClassNameMatcher matches for * deserialization, unless they are otherwise rejected. * * @param classNameMatcher the matcher to use */ public void accept(ClassNameMatcher classNameMatcher) /** * Accept class names that match the supplied pattern for * deserialization, unless they are otherwise rejected. * * @param pattern standard Java regexp */ public void accept(Pattern pattern) /** * Accept the wildcard specified classes for deserialization, * unless they are otherwise rejected. * * @param patterns Wildcard file name patterns as defined by * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch} */ public void accept(String... patterns) By default, the decoder will reject *all* classes that will be present in the incoming data. Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.

Created: 2024-12-26 Last update: 2025-01-14 11:30

2 security issues in bullseye high

There are 2 open security issues in bullseye.

1 important issue:

CVE-2024-52046: The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods: /** * Accept class names where the supplied ClassNameMatcher matches for * deserialization, unless they are otherwise rejected. * * @param classNameMatcher the matcher to use */ public void accept(ClassNameMatcher classNameMatcher) /** * Accept class names that match the supplied pattern for * deserialization, unless they are otherwise rejected. * * @param pattern standard Java regexp */ public void accept(Pattern pattern) /** * Accept the wildcard specified classes for deserialization, * unless they are otherwise rejected. * * @param patterns Wildcard file name patterns as defined by * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch} */ public void accept(String... patterns) By default, the decoder will reject *all* classes that will be present in the incoming data. Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.

1 issue postponed or untriaged:

CVE-2021-41973: (postponed; to be fixed through a stable update) In Apache MINA, a specifically crafted, malformed HTTP request may cause the HTTP Header decoder to loop indefinitely. The decoder assumed that the HTTP Header begins at the beginning of the buffer and loops if there is more data than expected. Please update MINA to 2.1.5 or greater.

Created: 2024-12-26 Last update: 2025-01-14 11:30

1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:

CVE-2024-52046: The ObjectSerializationDecoder in Apache MINA uses Java’s native deserialization protocol to process incoming serialized data but lacks the necessary security checks and defenses. This vulnerability allows attackers to exploit the deserialization process by sending specially crafted malicious serialized data, potentially leading to remote code execution (RCE) attacks. This issue affects MINA core versions 2.0.X, 2.1.X and 2.2.X, and will be fixed by the releases 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application using MINA core library will only be affected if the IoBuffer#getObject() method is called, and this specific method is potentially called when adding a ProtocolCodecFilter instance using the ObjectSerializationCodecFactory class in the filter chain. If your application is specifically using those classes, you have to upgrade to the latest version of MINA core library. Upgrading will not be enough: you also need to explicitly allow the classes the decoder will accept in the ObjectSerializationDecoder instance, using one of the three new methods: /** * Accept class names where the supplied ClassNameMatcher matches for * deserialization, unless they are otherwise rejected. * * @param classNameMatcher the matcher to use */ public void accept(ClassNameMatcher classNameMatcher) /** * Accept class names that match the supplied pattern for * deserialization, unless they are otherwise rejected. * * @param pattern standard Java regexp */ public void accept(Pattern pattern) /** * Accept the wildcard specified classes for deserialization, * unless they are otherwise rejected. * * @param patterns Wildcard file name patterns as defined by * {@link org.apache.commons.io.FilenameUtils#wildcardMatch(String, String) FilenameUtils.wildcardMatch} */ public void accept(String... patterns) By default, the decoder will reject *all* classes that will be present in the incoming data. Note: The FtpServer, SSHd and Vysper sub-project are not affected by this issue.

Created: 2024-12-26 Last update: 2025-01-14 11:30

lintian reports 6 warnings normal

Lintian reports 6 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2023-02-14 Last update: 2023-02-14 05:08

debian/patches: 3 patches to forward upstream low

Among the 4 debian patches available in version 2.2.1-3 of the package, we noticed the following issues:

3 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2023-02-26 15:54

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.0 instead of 4.6.2).

Created: 2024-04-07 Last update: 2024-04-07 13:15

news

[rss feed]

[2023-02-24] mina2 2.2.1-3 MIGRATED to testing (Debian testing watch)
[2023-02-13] Accepted mina2 2.2.1-3 (source) into unstable (Emmanuel Bourg)
[2023-01-21] mina2 2.2.1-2 MIGRATED to testing (Debian testing watch)
[2023-01-15] Accepted mina2 2.2.1-2 (source) into unstable (Emmanuel Bourg)
[2022-12-20] mina2 2.2.1-1 MIGRATED to testing (Debian testing watch)
[2022-12-15] Accepted mina2 2.2.1-1 (source) into unstable (Emmanuel Bourg)
[2022-06-20] mina2 2.1.6-1 MIGRATED to testing (Debian testing watch)
[2022-06-15] Accepted mina2 2.1.6-1 (source) into unstable (tony mancill)
[2021-12-07] mina2 2.1.5-1 MIGRATED to testing (Debian testing watch)
[2021-12-02] Accepted mina2 2.1.5-1 (source) into unstable (tony mancill)
[2021-05-11] mina2 2.1.4-2 MIGRATED to testing (Debian testing watch)
[2021-05-03] Accepted mina2 2.1.4-2 (source) into unstable (tony mancill)
[2020-10-23] mina2 2.1.4-1 MIGRATED to testing (Debian testing watch)
[2020-10-18] Accepted mina2 2.1.4-1 (source) into unstable (Markus Koschany)
[2018-12-09] mina2 2.0.19-2 MIGRATED to testing (Debian testing watch)
[2018-12-03] Accepted mina2 2.0.19-2 (source) into unstable (Emmanuel Bourg)
[2018-11-24] mina2 2.0.19-1 MIGRATED to testing (Debian testing watch)
[2018-11-19] Accepted mina2 2.0.19-1 (source) into unstable (Emmanuel Bourg)
[2018-09-03] mina2 2.0.16-3 MIGRATED to testing (Debian testing watch)
[2018-08-28] Accepted mina2 2.0.16-3 (source) into unstable (Markus Koschany)
[2017-10-01] mina2 2.0.16-2 MIGRATED to testing (Debian testing watch)
[2017-09-26] Accepted mina2 2.0.16-2 (source) into unstable (Emmanuel Bourg)
[2016-11-19] mina2 2.0.16-1 MIGRATED to testing (Debian testing watch)
[2016-11-13] Accepted mina2 2.0.16-1 (source all) into unstable (Emmanuel Bourg)
[2016-10-26] mina2 2.0.15-1 MIGRATED to testing (Debian testing watch)
[2016-10-20] Accepted mina2 2.0.15-1 (source all) into unstable (Emmanuel Bourg)
[2016-09-23] mina2 2.0.13-2 MIGRATED to testing (Debian testing watch)
[2016-09-18] Accepted mina2 2.0.13-2 (source all) into unstable (tony mancill)
[2016-05-09] mina2 2.0.13-1 MIGRATED to testing (Debian testing watch)
[2016-05-03] Accepted mina2 2.0.13-1 (source all) into unstable (Emmanuel Bourg)

bugs [bug history graph]

all: 1
RC: 1
I&N: 0
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (0, 6)
buildd: logs, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.2.1-3