• @franzfurdinand@lemmy.world
      link
      fedilink
      15
      edit-2
      1 month ago

      They’re sequential, so the values above and below yours are valid SSNs of people born in the same hospital around the same time.

      This would make it trivially easy to get access to records you shouldn’t

      • @asdfasdfasdf@lemmy.world
        link
        fedilink
        71 month ago

        Isn’t that assuming you have access to doing arbitrary SQL queries on the database? Then you’d by definition have access to records you shouldn’t.

        • borari
          link
          fedilink
          3
          edit-2
          1 month ago

          No. You can have control over specific parameters of an SQL query though. Look up insecure direct object reference vulnerabilities.

          Consider a website that uses the following URL to access the customer account page, by retrieving information from the back-end database: https://insecure-website.com/customer_account?customer_number=132355 Here, the customer number is used directly as a record index in queries that are performed on the back-end database. If no other controls are in place, an attacker can simply modify the customer_number value, bypassing access controls to view the records of other customers.

    • tiredofsametab
      link
      fedilink
      41 month ago

      As the user posted, one human can have more than one SSN in their lifetime. Many humans will never have an SSN. Some of those humans may have a TIN. Some humans may have at least one TIN and one SSN at some point.