<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>UPS on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/ups/</link>
    <description>Recent content in UPS on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 10 Apr 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/ups/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Breaking UPS Parcel Tracking</title>
      <link>https://insinuator.net/2024/04/breaking-ups-parcel-tracking/</link>
      <pubDate>Wed, 10 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/04/breaking-ups-parcel-tracking/</guid>
      <description>&lt;p&gt;Today, we describe our findings at United Parcel Service of America, Inc. (UPS), another German parcel market player, and the corresponding vulnerabilities’ disclosure process.&lt;/p&gt;&#xA;&lt;h1 id=&#34;findings&#34;&gt;Findings&lt;/h1&gt;&#xA;&lt;p&gt;Only a valid tracking number is needed to get the personal information of a parcel’s receiver, including the sender’s location, the recipient’s name, and the recipient’s location (city and country). It was possible to enumerate numerous tracking numbers during testing by iterating from known ones. Since the last digit of a tracking number is a checksum, it can be calculated. Also, certain businesses have a predefined prefix in their tracking numbers. This schema allows the enumeration of every parcel sent from a particular business.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
