{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12903 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-12903 and fix it if it is affected.\n\nWhat it is: CVE-2019-12903 is a medium-severity vulnerability in n/a, published on 19 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-12903 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-12903/ (Markdown: https://insights.sbomify.com/CVE-2019-12903/index.md)","id":"CVE-2019-12903","markdown":"https://insights.sbomify.com/CVE-2019-12903/index.md","name":"CVE-2019-12903","record":{"aliases":["GHSA-hgjj-fr5h-j9mv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pydio Cells","requires_auth":"low_privilege","summary":"Attackers can trigger error messages exposing database column and table names by sending unexpected Unicode input in the Name field.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cells","vendor":"pydio"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Pydio Cells before 1.5.0, when supplied with a Name field in an unexpected Unicode format, fails to handle this and includes the database column/table name as pert of the error message, exposing sensitive information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2019-12903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-12904"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-12902"},"products":["n/a"],"published":"2019-06-19","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-32749","kev_date_added":null,"published":"2023-06-08"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2019-12901","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2020-12851","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2020-12847","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7,"headline":"The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4.","id":"CVE-2020-12850","kev_date_added":null,"published":"2020-06-11"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2020-12852","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":6.5,"headline":"Server-side request forgery in n/a","id":"CVE-2023-32750","kev_date_added":null,"published":"2023-06-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can trigger error messages exposing database column and table names by sending unexpected Unicode input in the Name field.","url":"https://insights.sbomify.com/CVE-2019-12903/"}