CVE-2025-9785

{"id": "CVE-2025-9785", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-9785", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2025-09-04T03:55:27.125442Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "eb41dac7-0af8-4f84-9f6d-0272772514f4", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.7, "Automatable": "NOT_DEFINED", "attackVector": "ADJACENT", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "eb41dac7-0af8-4f84-9f6d-0272772514f4", "affectedData": [{"vendor": "PaperCut", "modules": ["Print Deploy"], "product": "Print Deploy", "versions": [{"status": "affected", "changes": [{"at": "1.9.2917", "status": "unaffected"}], "version": "0", "lessThan": "1.9.2917", "versionType": "custom"}], "platforms": ["Windows", "MacOS"], "defaultStatus": "unaffected"}]}], "published": "2025-09-03T05:15:30.910", "references": [{"url": "https://www.papercut.com/kb/Main/papercut-ng-mf-security-bulletin-september-2025/", "source": "eb41dac7-0af8-4f84-9f6d-0272772514f4"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "eb41dac7-0af8-4f84-9f6d-0272772514f4", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "PaperCut Print Deploy is an optional component that integrates with PaperCut NG/MF which simplifies printer deployment and management. When the component is deployed to an environment, the customer has an option to configure the system to use a self-signed certificate. If the customer does not fully configure the system to leverage the trust database on the clients, it opens up the communication between clients and the server to man-in-the-middle attacks.\u00a0\n\nIt was discovered that certain parts of the documentation related to the configuration of SSL in Print Deploy were lacking, which could potentially contribute to a misconfiguration of the Print Deploy client installation. PaperCut strongly recommends to use valid certificates to secure installations and to follow the updated documentation to ensure the correct SSL configuration. Those who use private CAs and/or self-signed certificates should make sure to copy their Certification Authority certificate, or their self signed certificate if using only one, to the trust store of their operating system and to the Java key store"}, {"lang": "es", "value": "PaperCut Print Deploy es un componente opcional que se integra con PaperCut NG/MF, lo que simplifica la implementaci\u00f3n y gesti\u00f3n de impresoras. Cuando el componente se implementa en un entorno, el cliente tiene la opci\u00f3n de configurar el sistema para usar un certificado autofirmado. Si el cliente no configura completamente el sistema para aprovechar la base de datos de confianza en los clientes, esto abre la comunicaci\u00f3n entre los clientes y el servidor a ataques man-in-the-middle.\n\nSe descubri\u00f3 que ciertas partes de la documentaci\u00f3n relacionada con la configuraci\u00f3n de SSL en Print Deploy eran deficientes, lo que podr\u00eda contribuir a una configuraci\u00f3n incorrecta de la instalaci\u00f3n del cliente de Print Deploy. PaperCut recomienda encarecidamente usar certificados v\u00e1lidos para proteger las instalaciones y seguir la documentaci\u00f3n actualizada para asegurar la configuraci\u00f3n SSL correcta. Aquellos que usan CA privadas y/o certificados autofirmados deben asegurarse de copiar su certificado de Autoridad de Certificaci\u00f3n, o su certificado autofirmado si usan solo uno, al almac\u00e9n de confianza de su sistema operativo y al almac\u00e9n de claves de Java."}], "lastModified": "2026-09-26T00:10:00.127", "sourceIdentifier": "eb41dac7-0af8-4f84-9f6d-0272772514f4"}