Skip to content
Unrated Medical device recall · FDA · Published August 15, 2019

Normand-Info Remisol Advance: Critical Remote Code Vulnerability Risk

Normand-Info recalls Remisol Advance devices running Windows XP, 7, Server 2003 or 2008 due to a critical remote code execution vulnerability that could allow attackers to take full control of the system without authentication.

🇺🇸 FDA recall #Z-1430-2020Medical deviceNormand-Info ›
Take action

Contact the company

Recalling firmNormand-Info S.A.S.U.7 rue Frederic Degeorge · Arras CEDEX, France
✎ GovInfoNow plain-language explainer

Normand-Info is recalling Remisol Advance devices running specific Windows versions because a security flaw could let attackers remotely take control of the system without needing a password. This affects users who need to keep their systems secure from potential hacking. Read more at govinfonow.com/recall/67170-normand-info-remisol-advance-critical-remote-code-vulnerability-risk.

Source Summary by GovInfoNow · govinfonow.com/recall/67170-normand-info-remisol-advance-critical-remote-code-vulnerability-risk · Updated August 19, 2026 · FDA enforcement record: FDA #Z-1430-2020

Cite this page

“Normand-Info Remisol Advance: Critical Remote Code Vulnerability Risk.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/67170-normand-info-remisol-advance-critical-remote-code-vulnerability-risk. Based on FDA recall #Z-1430-2020 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-1430-2020%22&limit=1).

The FDA announced on 2019-08-15 that Normand-Info S.A.S.U. is recalling Remisol Advance software running on Windows XP, Windows 7, Windows Server 2003 and Windows Server 2008 operating systems due to a critical remote code execution vulnerability. This defect allows attackers to execute arbitrary code without authentication. The FDA said the recall was voluntary.

How to tell if you have it

  • Brand: Normand-Info
  • Product: Remisol Advance
  • Operating Systems: Windows XP, Windows Server 2003, Windows 7, Windows Server 2008
  • Serial Numbers: All serial numbers
  • Units affected: 6479

The hazard

According to the FDA, a patch was released for a critical remote code execution vulnerability in remote desktop services that can be exploited remotely without authentication. An attacker who successfully exploits this vulnerability could execute arbitrary code on the target system, install programs, view, change, or delete data, or create new accounts with full user rights. If the vulnerability could be exploited locally, it would lock down the computer.

Context

GovInfoNow's records show Normand-Info S.A.S.U. has issued two other recalls since 2020-04-30. On 2021-03-22, the company recalled Remisol Advance Data Manager Software because incorrect rules may cause erroneous lab results. Another recall on 2020-04-30 involved Normand Info Remisol Advance Software 1.12, where incorrect blood test results risked deletion of repeated run data for WBC, UWBC and PLT.

How to tell if you have this one

Check if your Remisol Advance device runs Windows XP, Windows 7, Windows Server 2003, or Windows Server 2008. All devices with these operating systems are affected, as indicated by their serial numbers.

  • Brand
    Normand-Info
  • Category
    Medical device
Based on the official FDA remedy

What to do — step by step

  1. Update Security Software

    Install the latest security patches from the manufacturer to address the vulnerability.

Where it went and when

Where it was distributed

Distributed in 50 states and D.C..

Alaska: yesAKMaine: yesMEVermont: yesVTNew Hampshire: yesNHWashington: yesWAIdaho: yesIDMontana: yesMTNorth Dakota: yesNDMinnesota: yesMNIllinois: yesILWisconsin: yesWIMichigan: yesMINew York: yesNYRhode Island: yesRIMassachusetts: yesMAOregon: yesORNevada: yesNVWyoming: yesWYSouth Dakota: yesSDIowa: yesIAIndiana: yesINOhio: yesOHPennsylvania: yesPANew Jersey: yesNJConnecticut: yesCTCalifornia: yesCAUtah: yesUTColorado: yesCONebraska: yesNEMissouri: yesMOKentucky: yesKYWest Virginia: yesWVVirginia: yesVAMaryland: yesMDDelaware: yesDEArizona: yesAZNew Mexico: yesNMKansas: yesKSArkansas: yesARTennessee: yesTNNorth Carolina: yesNCSouth Carolina: yesSCDistrict of Columbia: yesDCOklahoma: yesOKLouisiana: yesLAMississippi: yesMSAlabama: yesALGeorgia: yesGAHawaii: yesHITexas: yesTXFlorida: yesFL

FDA distribution: “U.S.: NY, AZ, FL, NJ, MA, OH, CA, IL, NC, OK, IN, KY, OR, MI, WI, PA, UT, GA, VA, TX, NE, SD, IA, MN, MD, DE, SC, MT, WV, LA, MO, TN, NM, NV, HI, WA, WY, AL, AR, MS, RI, ID, ME, DC, ND, AK, CO, CT, KS, NH, VT” States read from FDA’s own wording; “not listed” means the notice does not name it.

States: Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, Delaware, District of Columbia, Florida, Georgia, Hawaii, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Montana, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Oregon, Pennsylvania, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, West Virginia, Wisconsin, Wyoming.

Recall timeline

FDA terminated this recall 22 months after the firm started it.

1. Firm started the recall: Aug 15, 201912. FDA classified it Class II: Mar 3, 202023. Published in FDA’s Enforcement Report: Mar 11, 202034. FDA terminated the recall: Jun 3, 2021420192021
  1. Firm started the recall
  2. FDA classified it Class II
  3. Published in FDA’s Enforcement Report
  4. FDA terminated the recall

Dates from the agency record only; steps without a date are left out.

Similar recalls

Latest medical device recalls

Keep exploring

Where this comes from

The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.

  • Official source: FDA Recall #Z-1430-2020 (August 15, 2019) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-1430-2020 to see it in context.
  • Plain-language summary written by qwen3:4b on August 19, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
  • GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.
GovInfoNow is an independent guide. We are not FDA or any government agency. Always confirm details with the official recall.Data: CPSC · FDA · NHTSA · USDA