Debian Package Tracker
Register | Log in
Subscribe

libio-socket-ssl-perl

Perl module implementing object oriented interface to SSL sockets

Choose email to subscribe with

general
  • source: libio-socket-ssl-perl (main)
  • version: 2.099-1
  • maintainer: Debian Perl Group (archive) (DMD) (LowNMU)
  • uploaders: Damyan Ivanov (DMD) – gregor herrmann (DMD) – Salvatore Bonaccorso (DMD) – Ansgar Burchardt (DMD) – Angel Abad (DMD) – Richard Hansen (DMD)
  • arch: all
  • std-ver: 4.7.4
  • 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.069-1
  • oldstable: 2.081-2
  • stable: 2.089-1
  • testing: 2.099-1
  • unstable: 2.099-1
versioned links
  • 2.069-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.081-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.089-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.099-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • libio-socket-ssl-perl (1 bugs: 0, 1, 0, 0)
action needed
2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:
  • CVE-2026-129891: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public suffix list because update_self_from_url fetches it over cleartext HTTP with no integrity check. Called with no argument, as the module's documentation shows, the updater fetches the list from the `http://` address in the URL constant and checks only that the request succeeded, with no signature or digest over the response. The lines that come back are written into the module's own source file as the built-in list. An attacker on the network path when the updater runs chooses the suffix boundary the module reports to every caller on the host, and that answer persists in the installed module until it is reinstalled. Dropping one rule makes the hostname check in IO::Socket::SSL accept a wildcard certificate that spans the whole public suffix that rule named.
  • CVE-2026-129892: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl allow code injection via a fetched list line that closes the built-in data heredoc when update_self_from_url rewrites the module's source. The rewrite copies the module's source down to the built-in list's heredoc and appends each fetched line below it. Nothing checks that a line looks like a domain. A line that is not a comment loses only what follows a `//` and its trailing whitespace, so a line reading END_BUILTIN_DATA is appended as it stands and ends the data block in the rewritten file. Every fetched line after it is Perl. Arbitrary Perl runs in every process that loads IO::Socket::SSL, which loads this module unconditionally, until the file is reinstalled. The attacker must control the fetched list, through the cleartext default URL or a caller-supplied one, and the updater must run with write access to the installed module.
Created: 2026-11-18 Last update: 2026-11-18 07:01
2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:
  • CVE-2026-129891: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public suffix list because update_self_from_url fetches it over cleartext HTTP with no integrity check. Called with no argument, as the module's documentation shows, the updater fetches the list from the `http://` address in the URL constant and checks only that the request succeeded, with no signature or digest over the response. The lines that come back are written into the module's own source file as the built-in list. An attacker on the network path when the updater runs chooses the suffix boundary the module reports to every caller on the host, and that answer persists in the installed module until it is reinstalled. Dropping one rule makes the hostname check in IO::Socket::SSL accept a wildcard certificate that spans the whole public suffix that rule named.
  • CVE-2026-129892: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl allow code injection via a fetched list line that closes the built-in data heredoc when update_self_from_url rewrites the module's source. The rewrite copies the module's source down to the built-in list's heredoc and appends each fetched line below it. Nothing checks that a line looks like a domain. A line that is not a comment loses only what follows a `//` and its trailing whitespace, so a line reading END_BUILTIN_DATA is appended as it stands and ends the data block in the rewritten file. Every fetched line after it is Perl. Arbitrary Perl runs in every process that loads IO::Socket::SSL, which loads this module unconditionally, until the file is reinstalled. The attacker must control the fetched list, through the cleartext default URL or a caller-supplied one, and the updater must run with write access to the installed module.
Created: 2026-11-18 Last update: 2026-11-18 07:01
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2026-129891: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public suffix list because update_self_from_url fetches it over cleartext HTTP with no integrity check. Called with no argument, as the module's documentation shows, the updater fetches the list from the `http://` address in the URL constant and checks only that the request succeeded, with no signature or digest over the response. The lines that come back are written into the module's own source file as the built-in list. An attacker on the network path when the updater runs chooses the suffix boundary the module reports to every caller on the host, and that answer persists in the installed module until it is reinstalled. Dropping one rule makes the hostname check in IO::Socket::SSL accept a wildcard certificate that spans the whole public suffix that rule named.
  • CVE-2026-129892: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl allow code injection via a fetched list line that closes the built-in data heredoc when update_self_from_url rewrites the module's source. The rewrite copies the module's source down to the built-in list's heredoc and appends each fetched line below it. Nothing checks that a line looks like a domain. A line that is not a comment loses only what follows a `//` and its trailing whitespace, so a line reading END_BUILTIN_DATA is appended as it stands and ends the data block in the rewritten file. Every fetched line after it is Perl. Arbitrary Perl runs in every process that loads IO::Socket::SSL, which loads this module unconditionally, until the file is reinstalled. The attacker must control the fetched list, through the cleartext default URL or a caller-supplied one, and the updater must run with write access to the installed module.
Created: 2026-11-18 Last update: 2026-11-18 07:01
2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:
  • CVE-2026-129891: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl let an on-path attacker choose the installed public suffix list because update_self_from_url fetches it over cleartext HTTP with no integrity check. Called with no argument, as the module's documentation shows, the updater fetches the list from the `http://` address in the URL constant and checks only that the request succeeded, with no signature or digest over the response. The lines that come back are written into the module's own source file as the built-in list. An attacker on the network path when the updater runs chooses the suffix boundary the module reports to every caller on the host, and that answer persists in the installed module until it is reinstalled. Dropping one rule makes the hostname check in IO::Socket::SSL accept a wildcard certificate that spans the whole public suffix that rule named.
  • CVE-2026-129892: IO::Socket::SSL::PublicSuffix versions through 2.099 for Perl allow code injection via a fetched list line that closes the built-in data heredoc when update_self_from_url rewrites the module's source. The rewrite copies the module's source down to the built-in list's heredoc and appends each fetched line below it. Nothing checks that a line looks like a domain. A line that is not a comment loses only what follows a `//` and its trailing whitespace, so a line reading END_BUILTIN_DATA is appended as it stands and ends the data block in the rewritten file. Every fetched line after it is Perl. Arbitrary Perl runs in every process that loads IO::Socket::SSL, which loads this module unconditionally, until the file is reinstalled. The attacker must control the fetched list, through the cleartext default URL or a caller-supplied one, and the updater must run with write access to the installed module.
Created: 2026-11-18 Last update: 2026-11-18 07:01
version in VCS is newer than in repository, is it time to upload? normal
vcswatch reports that this package seems to have a new changelog entry (version 2.099-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:
commit b10c1ffc69f0efaa5dc3e7b09888c8e2bc3b5e44
Author: gregor herrmann <gregoa@debian.org>
Date:   Sun Nov 8 00:32:28 2026 +0100

    update changelog
    
    Gbp-Dch: Ignore

commit 8dafa37188d5b144755ac05b02b22925224f5c7c
Author: gregor herrmann <gregoa@debian.org>
Date:   Sun Nov 8 00:32:28 2026 +0100

    Convert debian/watch to version 5.
Created: 2026-11-08 Last update: 2026-11-16 15:31
lintian reports 1 warning normal
Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.
Created: 2026-07-06 Last update: 2026-07-06 09:17
news
[rss feed]
  • [2026-07-08] libio-socket-ssl-perl 2.099-1 MIGRATED to testing (Debian testing watch)
  • [2026-07-05] Accepted libio-socket-ssl-perl 2.099-1 (source) into unstable (gregor herrmann)
  • [2026-01-09] libio-socket-ssl-perl 2.098-1 MIGRATED to testing (Debian testing watch)
  • [2026-01-07] Accepted libio-socket-ssl-perl 2.098-1 (source) into unstable (gregor herrmann)
  • [2025-08-21] libio-socket-ssl-perl 2.095-1 MIGRATED to testing (Debian testing watch)
  • [2025-08-17] Accepted libio-socket-ssl-perl 2.095-1 (source) into unstable (Salvatore Bonaccorso)
  • [2024-09-04] libio-socket-ssl-perl 2.089-1 MIGRATED to testing (Debian testing watch)
  • [2024-09-01] Accepted libio-socket-ssl-perl 2.089-1 (source) into unstable (Salvatore Bonaccorso)
  • [2024-07-25] libio-socket-ssl-perl 2.088-1 MIGRATED to testing (Debian testing watch)
  • [2024-07-23] Accepted libio-socket-ssl-perl 2.088-1 (source) into unstable (Salvatore Bonaccorso)
  • [2024-01-29] libio-socket-ssl-perl 2.085-1 MIGRATED to testing (Debian testing watch)
  • [2024-01-27] Accepted libio-socket-ssl-perl 2.085-1 (source) into unstable (gregor herrmann)
  • [2023-11-12] libio-socket-ssl-perl 2.084-1 MIGRATED to testing (Debian testing watch)
  • [2023-11-10] Accepted libio-socket-ssl-perl 2.084-1 (source) into unstable (gregor herrmann)
  • [2023-06-17] libio-socket-ssl-perl 2.083-1 MIGRATED to testing (Debian testing watch)
  • [2023-06-12] Accepted libio-socket-ssl-perl 2.083-1 (source) into unstable (Salvatore Bonaccorso)
  • [2023-02-26] libio-socket-ssl-perl 2.081-2 MIGRATED to testing (Debian testing watch)
  • [2023-02-04] Accepted libio-socket-ssl-perl 2.081-2 (source) into unstable (Salvatore Bonaccorso)
  • [2023-02-04] Accepted libio-socket-ssl-perl 2.081-1 (source) into unstable (Salvatore Bonaccorso)
  • [2023-01-01] libio-socket-ssl-perl 2.078-1 MIGRATED to testing (Debian testing watch)
  • [2022-12-15] Accepted libio-socket-ssl-perl 2.078-1 (source) into unstable (Salvatore Bonaccorso)
  • [2022-11-27] libio-socket-ssl-perl 2.077-1 MIGRATED to testing (Debian testing watch)
  • [2022-11-24] Accepted libio-socket-ssl-perl 2.077-1 (source) into unstable (Salvatore Bonaccorso)
  • [2022-11-18] libio-socket-ssl-perl 2.076-1 MIGRATED to testing (Debian testing watch)
  • [2022-11-14] Accepted libio-socket-ssl-perl 2.076-1 (source) into unstable (Salvatore Bonaccorso)
  • [2022-09-09] libio-socket-ssl-perl 2.075-1 MIGRATED to testing (Debian testing watch)
  • [2022-09-07] Accepted libio-socket-ssl-perl 2.075-1 (source) into unstable (Salvatore Bonaccorso)
  • [2022-01-16] libio-socket-ssl-perl 2.074-2 MIGRATED to testing (Debian testing watch)
  • [2022-01-13] Accepted libio-socket-ssl-perl 2.074-2 (source) into unstable (gregor herrmann)
  • [2022-01-11] libio-socket-ssl-perl 2.074-1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 1
  • RC: 0
  • I&N: 1
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian (0, 1)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.099-1
  • 3 bugs

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing